-
Suggestion
-
Resolution: Deployed
-
321
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hey everyone,
We are happy to announce that the rollout of group rename feature has been finished to 100% of all organizations on the new administration experience, hence, after 20 years and cake 9 days, we will finally close this feature request for cloud.
A good reminder that there are still dependencies in Jira to make group rename perfect, and those are tracked in detail on Group Rename dependencies tracking (ID-8092).
For those customers still on the legacy administration experience, we are committed to unblock you, all dependencies for migration into the new experience should be addressed throughout 2023, current end date on December, as a dependency is unblocked and shipped to production, we will already migrate the organizations that were unblocked. Please, feel free to ask your questions or concerns on this ticket, even after it is closed, I will commit to answer any questions for the time being on a best effort.
Thank you, as always.
RODRIGO BECKER
Product Lead, Atlassian Access
Original request description:
As a JIRA administrator I am responsible for managing a large installation with multiple users and groups. Given the dynamic nature of my environment it is very difficult for me to create the correct user group name which can be used for many projects later on. I need to be able to rename the user groups, to reflect the changes my organisation undergoes.
- has a derivative of
-
ID-8234 Tracking Support cases where customers cannot rename a group due to using old user management
- Gathering Interest
- is duplicated by
-
JRACLOUD-59541 jira user and group administration
- Closed
-
CONFCLOUD-73404 Allow site admin group name to be renamed
- Gathering Interest
- is incorporated by
-
JRACLOUD-13297 SOAP Service Improvements - Especially with user management
- Closed
- is related to
-
CWD-4763 Inability for Crowd to detect renamed LDAP groups as Crowd does not track using its LDAP IDs yet
- Closed
-
JRACLOUD-10100 Add ability to copy groups
- Closed
-
JRASERVER-72769 Provide the ability to rename groups after creation
- Gathering Interest
-
ID-126 Bulk Add and Remove Users to and from Multiple Groups
- Gathering Interest
-
ACCESS-800 Ability to rename groups after they've synced to the organization from an identity provider.
- Under Consideration
-
JRASERVER-1391 Provide the ability to rename groups after creation
- Under Consideration
- relates to
-
JRACLOUD-1549 Ability to rename a user
- Closed
-
JRACLOUD-36637 When deleting a group, I should be prompted to change the sharing information for dashboards and filters
- Closed
-
ID-149 Renaming of groups should be possible
- Closed
-
CWD-1599 Ability to rename groups
- Under Consideration
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...