• Hide
      Atlassian Update – 30 May 2025

      Hello all,

      Took a while longer but here I am to bring you good news.

      Our teams have roadmapped both dependencies below to start work in the next quarter and hopefully deliver by then, as done before, I will continue monitoring and keeping you up to date if there are blockers or risks.

      Thank you!

      RODRIGO BECKER
      Product Lead, Atlassian Guard

      Show
      Atlassian Update – 30 May 2025 Hello all, Took a while longer but here I am to bring you good news. Our teams have roadmapped both dependencies below to start work in the next quarter and hopefully deliver by then, as done before, I will continue monitoring and keeping you up to date if there are blockers or risks. Thank you! RODRIGO BECKER Product Lead, Atlassian Guard
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Hi everyone,

      We've launched the feature to rename groups in Atlassian Cloud, as per ID-6677.

      As we informed in the above suggestion ticket, we decided to launch the feature in its earlier stages, as we know it can already benefit many of our customers, and, continue to work on the remaining dependencies, prioritizing the most impactful to the least, based on our usability analytics research.

      On this ticket, we will track each dependency, to give you full visibility of what the work looks like, and what we are doing. The purpose of this ticket is not to gather impact, or prioritize work, the group rename feature is already a priority for Atlassian, and critical part of our roadmap.

      Id Depedency Status
      1 Product Access Done
      2 Global permission Done
      3 Advanced Roadmaps - Plugin Permissions Done
      4 Project Roles Done
      5 Notification Done
      6 Issue Securities Scheme Done
      7 Share Permission Done
      8 JQL Filters - Subscription Done
      9 Permissions Scheme Done
      10 Advanced Roadmaps - Plan Done
      11 Workflows Done
      12 Announcements Deprecated
      13 Issue Comments Done
      14 User Picker Filter Done
      15 Board Administrators Done
      16 Worklogs Done
      17 Group Pickers - Custom Fields Done
      18 JSM Assets Scheduled
      19 JSM Approvals - Group Pickers Scheduled
      20 Automation platform experiences Done

      JQL Filter - Results are out of scope due to complexity in being a string that would need to change per JQL in the database, meanwhile, we know it's difficult to identify the blocking JQL, please use the workaround available in ID-8534.

      Looking for user provisioning via SCIM group rename? Once all dependencies are fixed, we should start work on ACCESS-800.

      Thank you!

      RODRIGO BECKER
      Product Lead, Atlassian Access

            [AX-159] Group Rename dependencies tracking

            Pinned comments

            Pinned by Rodrigo B.

            Rodrigo B. added a comment -
            Atlassian Update – 30 May 2025

            Hello all,

            Took a while longer but here I am to bring you good news.

            Our teams have roadmapped both dependencies below to start work in the next quarter and hopefully deliver by then, as done before, I will continue monitoring and keeping you up to date if there are blockers or risks.

            Thank you!

            RODRIGO BECKER
            Product Lead, Atlassian Guard

            Rodrigo B. added a comment - Atlassian Update – 30 May 2025 Hello all, Took a while longer but here I am to bring you good news. Our teams have roadmapped both dependencies below to start work in the next quarter and hopefully deliver by then, as done before, I will continue monitoring and keeping you up to date if there are blockers or risks. Thank you! RODRIGO BECKER Product Lead, Atlassian Guard

            All comments

            Hi

            Thanks for the rename of groups but having some sync issues with Jira global permission schema

            Found out on Jira Cloud Global permissions its not updating the group names when renamed on Atlassian
            Possible this is just a matter of time for sync to happen, im not sure please guide on this
            Not great when this changes could affect a lot of users if not synced

            When i looked at the links to find the group on the Atlassian i could see groupid="Name on the group"
            https://xxx.atlassian.net/secure/admin/user/UserBrowser.jspa?group=administrators

            Would suggest that the groups get changed to GroupID"ID number of the group" so its not depending on the group name
            This would maybe also solve the group name lookup

            But now im afraid that i messed something up by changing some group names thats not great

            Rasmus Breidahl added a comment - Hi Thanks for the rename of groups but having some sync issues with Jira global permission schema Found out on Jira Cloud Global permissions its not updating the group names when renamed on Atlassian Possible this is just a matter of time for sync to happen, im not sure please guide on this Not great when this changes could affect a lot of users if not synced When i looked at the links to find the group on the Atlassian i could see groupid="Name on the group" https://xxx.atlassian.net/secure/admin/user/UserBrowser.jspa?group=administrators Would suggest that the groups get changed to GroupID"ID number of the group" so its not depending on the group name This would maybe also solve the group name lookup But now im afraid that i messed something up by changing some group names thats not great

            Rodrigo B. added a comment -

            Hi 9f4060b22593,

            I did not miss your message, my friend! Thanks for the patience so far.

            Currently I am focusing on this main dependency ticket as best effort to keep you all updated, but that one is the next in line for me. Gladly, I chased up information with our amazing R&D team since your message and this work is already roadmapped/scheduled.

            The tricky part is that the SCIM service is ongoing a re-architecture so it's more flexible and powerful to serve our customers, unlocking features like group rename more reliably. Estimated delivery is at May-June, 2026, but there is an available workaround by contacting Atlassian support.

            Thank you again,

            Rodrigo Becker
            Product Lead, Atlassian Guard

            Rodrigo B. added a comment - Hi 9f4060b22593 , I did not miss your message, my friend! Thanks for the patience so far. Currently I am focusing on this main dependency ticket as best effort to keep you all updated, but that one is the next in line for me. Gladly, I chased up information with our amazing R&D team since your message and this work is already roadmapped/scheduled. The tricky part is that the SCIM service is ongoing a re-architecture so it's more flexible and powerful to serve our customers, unlocking features like group rename more reliably. Estimated delivery is at May-June, 2026, but there is an available workaround by contacting Atlassian support . Thank you again, Rodrigo Becker Product Lead, Atlassian Guard

            Pinned by Rodrigo B.

            Rodrigo B. added a comment -
            Atlassian Update – 30 May 2025

            Hello all,

            Took a while longer but here I am to bring you good news.

            Our teams have roadmapped both dependencies below to start work in the next quarter and hopefully deliver by then, as done before, I will continue monitoring and keeping you up to date if there are blockers or risks.

            Thank you!

            RODRIGO BECKER
            Product Lead, Atlassian Guard

            Rodrigo B. added a comment - Atlassian Update – 30 May 2025 Hello all, Took a while longer but here I am to bring you good news. Our teams have roadmapped both dependencies below to start work in the next quarter and hopefully deliver by then, as done before, I will continue monitoring and keeping you up to date if there are blockers or risks. Thank you! RODRIGO BECKER Product Lead, Atlassian Guard

            Tobias H added a comment -

            rbecker Thank you for the update! Would you be able to provide some insight on the status of https://jira.atlassian.com/browse/ACCESS-800 as well? The assignee is inactive and we are all waiting for updates over there

            Tobias H added a comment - rbecker Thank you for the update! Would you be able to provide some insight on the status of https://jira.atlassian.com/browse/ACCESS-800 as well? The assignee is inactive and we are all waiting for updates over there

            Rodrigo B. added a comment -

            Hi everyone,

            A quick update on this ticket about JSM Approvals - Group Pickers, we've received reports that this was not working as expected and upon verifying, it is still an unsolved dependency currently on pause, we will pick up from your feedback here to bring to our R&D and understand if this can be re-prioritized.

            Apologies for the confusion this has caused! I will share another update in 2 weeks.

            Thank you!

            Rodrigo Becker

            Rodrigo B. added a comment - Hi everyone, A quick update on this ticket about JSM Approvals - Group Pickers , we've received reports that this was not working as expected and upon verifying, it is still an unsolved dependency currently on pause , we will pick up from your feedback here to bring to our R&D and understand if this can be re-prioritized. Apologies for the confusion this has caused! I will share another update in 2 weeks. Thank you! Rodrigo Becker

            Hey rbecker 

            According to the October'24 update, JSM Approvals - Group Pickers are fixed and should not block renaming groups anymore.

            Well well well...

             

            To edit this group name, first remove the group from the following Jira settings:
            my-sandbox.atlassian.net
            JSM Approvals - Group Picker Custom Fields 

            We now use the managed teams feature to link Atlassian teams to our groups. We need this in order to release Platform Experiences to our company. We encourage our users to use groups wherever possible. If we cannot rename groups anymore because they are used for approvals, that's bad.

             

            Can I please get an info on why this is an issue again?

            Jared Schmitt added a comment - Hey rbecker   According to the October'24 update, JSM Approvals - Group Pickers are fixed and should not block renaming groups anymore. Well well well...   To edit this group name, first remove the group from the following Jira settings: my-sandbox.atlassian.net JSM Approvals - Group Picker Custom Fields We now use the managed teams feature to link Atlassian teams to our groups. We need this in order to release Platform Experiences to our company. We encourage our users to use groups wherever possible. If we cannot rename groups anymore because they are used for approvals, that's bad.   Can I please get an info on why this is an issue again?

            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

            Rodrigo B. added a comment - 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

            Tobias H added a comment -

            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? 

            Tobias H added a comment - 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? 

            Rodrigo B. added a comment -

            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

            Rodrigo B. added a comment - 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  

            Jared Schmitt added a comment - 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  

              rbecker Rodrigo B.
              rbecker Rodrigo B.
              Votes:
              172 Vote for this issue
              Watchers:
              208 Start watching this issue

                Created:
                Updated: