Hi 9f4060b22593,

Not exactly, most of the work for ACCESS-800 is already done, but we cannot deploy in production because of these dependencies that could cause a disconnect between IdP and the Atlassian cloud userbase.

My focus is on this ticket at the moment, but I will take a look at the other one again and get back on that ticket in a few weeks.

Thank you,

RODRIGO BECKER
Product Lead, Atlassian Access

Just so I understand, rbecker, work on https://jira.atlassian.com/browse/ACCESS-800 won't start until this is completed?
So we are still looking for roughly another year or so until we can rename IdP synced groups? 

Hi 59886a7e4545,

I checked in with the team, JSM Assets is in progress but estimated delivery date is Q2 2025 at the moment, the work was not trivial as they needed to do a re-architecture of the service which is still in progress, I will update this ticket and get back here if anything changes!

Thanks for the nudge,

RODRIGO BECKER
Product Lead, Atlassian Access

Hi rbecker 

Thanks a lot for the update. Glad to hear that 19 and 20 haven been done!

Any news on 18? Just a rough ETA, we'll add another 1-2 month ourselves  

Hi 3870977af899 & 59886a7e4545,

That Automation platform experiences dependency was delivered a month after the original estimated date, end of August, thanks for the nudge here, I am updating the ticket to reflect that, in case you still see any issues, please contact our support on support.atlassian.com.

Thank you for your patience!

RODRIGO BECKER
Product Lead, Atlassian Access

Hi 6c265266a838,

I know it's been a while, but I hope that you managed to get help from our support to clean up any references from JSM Assets that blocked you from renaming the group, if not, don't hesitate on asking for our help on support.atlassian.com.

Thank you,

RODRIGO BECKER
Product Lead, Atlassian Access

 

Hi rbecker ,

any updates when 20 will be delivered?
I need to update group names very soon and those not being updated automatically in the automations will lead to quite a few issues.

Thanks,
Jana

Hi rbecker 

20 should have been delivered by EoM July, it's September now and no update on the matter.

When can we expect 20 to be done, 18 and 19 to be (a) started and (b) resolved?

When you get to JSM Assets, please take into account if you don't have JSM premium (and so not using assets). I've tried to rename a group we use in our JSM. We are not running premium and so don't have access to assets, but won't let me rename it as I first have to remove it from the CMDB - Assets setting. When I click on this link, I get the try premium for free window (https://alayacare.atlassian.net/jira/servicedesk/assets)

Hi rbecker,
Thanks for the updates.

I would appreciate it if you could provide an update/ETA on the "JSM Assets" dependency in your next update. 
We changed the site name and are unable to rename our JSM user group, which still references the old name due to this dependency. Is there a workaround for renaming a group that has a dependency on "CMDB—Asset"? I manually looked through the asset configurations but could not find any reference to the group.

Thanks,

Milad

rbecker 
Good news would be if you get the whole functionality finally really fixed!
It took you almost 20 years to deliver ID-6677 Renaming groups after creation. - Create and track feature requests for Atlassian products. at least as a Beta, what is it now for more than one year without any further progress.
The missing functionality for assets is already known since 15/03/2023 according to Atlassian organization admins can now rename groups in cloud.
So I'm curious if it will really be delivered without any further bugs with July and even how much years it will take to fix the other open points?

This is FINALLY available in our instance! 

Navigate to Atlassian Administration > Directory > Groups > [Group]

There is a new option under the ... (ellipsis) menu to Edit Group Name.

If the group is associated with any Jira queries/items, you will get a notification that the group name cannot be changed.

Hi fd18b389d3c8,

Thanks to the great contributions of fdd9d54b8b81 and dec7a92259f7, you have a few options, our support is always happy to assist in such cases as we know they are pain points and limitations in our product, but feel free to implement your own solution as well!

Thank you,

RODRIGO BECKER
Product Lead, Atlassian Access

Hello David,

Recently I ran into the same problem and found some JQL in the filters contained the function "membersOf". I wrote a python script against the Jira API to search for the text "membersOf" in the JQL.

API: rest/api/3/filter/search?expand=jql

A simple search (e.g. Ctrl + F) through the results, should show you which filters you need to adjust.

Hello Rodrigo,
Thank you for the update!
Unfortunately, I have the same problem as Thomas. Cannot rename the group cause it's used in the JQL filters.
It's really hard to find which filters are used by the group when the lists contain hundreds of filters.

Thank you Rodrigo for your feedback - Although solving dependencies in the JQL filters and JSD serieses doesn't work automatically when renaming, we could solve the dependency issue with the help of the Atlassian Support. We simply asked which filters and serieses were blocking the group rename and could resolve them manually. Finding the 3 problematic filters out of the 1000+ filters on our instance would've taken a lot of time manually without the help of the support. Just as an information in case anybody runs into the same problems we ran into.

Hi 45b95255591e, fd18b389d3c8 and be6df64da5ff,

You are right to have noted that this ticket only includes Jira dependencies, the reason for that is because Confluence dependencies were already resolved in 2022, if you are facing issues in Confluence after renaming a group, please raise a support ticket to our team so we can validate the problem.

Thank you for reporting any issues here as well.

RODRIGO BECKER
Product Lead, Atlassian Access

Hi fdd9d54b8b81,

Thanks for bringing your question again, apologize for missing it earlier.

Experiences related to the JQL themselves are considered unaddressable at this time, as they are purely strings on our product's database, switching the group name for the ID would cause confusion for end users, also, the level of complexity and risk to perform a widespread string replacement to all databases was evaluated and ruled out.

We don't have plans on our roadmap to address the JQL engine now, but I will keep an eye on this once we ship all dependencies in scope.

I know this isn't the answer you were looking for, but we always want to give as much transparency as we can into giving realistic expectations.

Thank you & keep contributing to this ticket!

RODRIGO BECKER
Product Lead, Atlassian Access
 

I also had questions about how Confluence will work with this. For what it's worth, I did the following test and it worked fine: 

1. created a test group
2. added the test group to a space's permissions and a page's permissions
3. renamed the group
4. verified that it updated in both the space and page's permissions and it did (after a couple of min)

So it seems to me that it is working with Confluence as well.

I have the same question as Dirk - what about Confluence dependencies? Lost page restrictions based on groups are almost impossible to restore.

This all looks like Jira stuff. What about usage in confluence (spaces and page restrictions!). The wasted page restrictions because of rename a group is really a hell to fix...

Hi,

asking again as I got no reply on my last comment; is there an intention to allow group renaming if there are dependencies in JQL Filter results and JSD serieses? If not, is there another ticket that we can vote for? See screenshot below

Hi,

will Dependencies of type "JSD - Series" and "JQL Filters - Result" also be solved automatically when the ticket is done? I could not find these entries in the table above.

Hi 9f4ac742e4d6,

We are on track for December to deliver all dependencies, the group rename feature is one of the main blockers to migrate our customers to the new administration experience (Where group rename exists), but the delivery date to migrate all customers is uncertain, given that there are other dependencies in place, but our hopes are to have everyone in the new administration experience by end of March, 2023 2024, at the moment, though we should slowly migrate customers until that date as it becomes possible.

I hope this gives clarity to your question!

RODRIGO BECKER
Product Lead, Atlassian Access

When will we all be able to actually change the group names?

Hey hey Rodrigo - just raised a support request now.

Hello d8d00dff5256,

Thanks for bringing this issue forth!

Would you mind raising a support request about it on https://support.atlassian.com/contact/? If there is an inconsistency with our dependency checks, we will need to diagnose it to understand how we can fix it for you and others, if you already did that, thank you again!

RODRIGO BECKER
Product Lead, Atlassian Access

Hey Rodrigo (I cannot at-mention you here?) .... the rename is NOT WORKING against Workflows I'm afraid.

I'm trying to rename a key group we've had since Server .... and hitting rename group told me that some Filters contained the group, and some Workflows also did.

I've fixed the Filters, and can see they are no longer reported as containing the group, however I cannot fix the Workflows.

I've exported all Workflows as XML, then searched using a multi-file text editor, and fixed two occurences of the group and saved the Workflows.

I've then tried to rename the group again - but failing every time on Workflows, despite it not being present.

When will we be able to actually change the group names?

So we're just continuing to ignore your Data Center customers that have been asking for this ability for 20 years?  And that isn't an exaggeration.  

JRASERVER-1391 has been open for 20 years.

Hi everyone,

Stay tuned as the update for this ticket will come out tomorrow, we are just verifying a few things before to ensure we are sharing as much as possible!

Thank you!

RODRIGO BECKER
Product Lead, Atlassian Access

Hi. I just recently had this rolled out on our instance. I wonder why this isnt in another comment here but shouldn't automation item be added to the table here as per the last update on https://community.atlassian.com/t5/Atlassian-Access-articles/Org-admins-can-now-rename-groups-in-cloud/ba-p/2276321 - Looking forward to these updates. Thank you

Any progress on this? I see the table was last updated in Mar 2023. Thank you

@Milad: When a group has a certain dependency that isn't resolved yet, then you'll see a popup listing those dependencies preventing you from renaming that group. So, you can't edit the group unless the dependency is fixed, or you manually remove that piece of configuration. Example: https://jira.atlassian.com/browse/ID-6677?focusedCommentId=3259371&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3259371

@Rodrigo: I second Milad's comment, thanks for updates (and the dev team's work!) and following up from my linked comment, I can already rename some of the groups that were previously blocked, which is great!

Hi Rodrigo B.,

I want to say thanks and also appreciate the regular updates and your communication style regarding this piece of work. 

May I know the actual impact of editing the group name while they are still dependencies in work? For example, what will happen (or what is not happening) regarding "Group Pickers - Custom Fields" if I edit a group name now? And are you going to eventually backtrack/fix those inconsistencies that occur during this period of time (till the end of June)? I searched the comments of this ticket and ID-6677, but could not find this info.

Kind regards,

Milad

Hi ce2e2516fe3a,

Thanks for the question, I've updated this ticket's linked issues, as well as added a message regarding provisioned group renaming to the description of this ticket. The ticket to follow is ACCESS-800, and it is currently blocked by this one. We don't have updates for that one yet, as all relevant updates will be on this ticket, being the main blocker.

I hope that clarifies!

RODRIGO BECKER
Product Lead, Atlassian Access

Is this the ticket to watch for readiness of group renaming via provisioned groups (e.g. from Azure AD)?

Hi everyone,

Quick update, we had the dependency for Project Roles done, but it wasn't deployed to production yet, it should be done in the following days. Sorry for any trouble!

See ya!

RODRIGO BECKER
Product Lead, Atlassian Access

Hi 38f2f35e1866, this ticket does not address Server/DC sorry.

You'll still need to follow https://jira.atlassian.com/browse/JRASERVER-1391 for that

Will this issue be addressed also in the Data Center version?

Thanks for this ticket and the details. Yeah, the visibilty is great and looking forward to all of this being rolled out. Thank you, Atlassian.

I love this visibility! I hope you guys do this for ALL the bugs/features tickets that are being worked on. This is really helpful! Great job!

Thank you!!