Details
-
Suggestion
-
Status: In Progress (View Workflow)
-
Resolution: Unresolved
-
None
-
14
-
Description
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 | In Progress |
| 6 | Issue Securities Scheme | To Do |
| 7 | Share Permission | In Progress |
| 8 | JQL Filters - Subscription | Done |
| 9 | Permissions Scheme | In Progress |
| 10 | Advanced Roadmaps - Plan | In Progress |
| 11 | Workflows | In Progress |
| 12 | Announcements | To Do |
| 13 | Issue Comments | In Progress |
| 14 | User Picker Filter | Done |
| 15 | Board Administrators | To Do |
| 16 | Worklogs | To Do |
| 17 | Group Pickers - Custom Fields | In Progress |
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
Attachments
Issue Links
- blocks
-
- Under Consideration