-
Suggestion
-
Resolution: Unresolved
-
139
-
-
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 | In progress |
19 | JSM Approvals - Group Pickers | Done |
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
- blocks
-
ACCESS-800 Ability to rename groups after they've synced to the organization from an identity provider.
- In Progress
- is related to
-
JRACLOUD-83598 Announcements dependency for Group rename
-
- Closed
-
-
CONFCLOUD-80746 Reflect group name changes to the setting of Restricted Pages
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[ID-8092] Group Rename dependencies tracking
All comments
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?