Details
-
Suggestion
-
Status: In Progress (View Workflow)
-
Resolution: Unresolved
-
249
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hello everyone,
We bring good news, this feature is under development by a dedicated team, and we are currently on track to get it ready by the end of the year, in December, 2022.
We will maintain monthly updates to inform you the status of our progress (good or bad news), and in the spirit of our values, we want to be open with you. This has been a challenging problem to solve due to the complexity of the products themselves, and we wanted to find a solution that matches the future state of the administration experience for all of our Atlassian Cloud services. But we are happy and confident with the solution explored and chosen, hence we are coming back to you now.
We sincerely thank you for your patience, and stay tuned for another update by October 14th,
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.
Attachments
Issue Links
- is duplicated by
-
- Closed
-
- Gathering Interest
- is incorporated by
-
- Closed
- is related to
-
CWD-4763 Inability for Crowd to detect renamed LDAP groups as Crowd does not track using its LDAP IDs yet
-
- Long Term Backlog
-
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Under Consideration
-
- Under Consideration
- relates to
-
- Closed
-
- Closed
-
- Closed
-
- Under Consideration
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
