-
Suggestion
-
Resolution: Unresolved
-
None
-
109
-
Atlassian Update – 30 October 2024
Hi everyone,
Sorry for the radio silence, but good things still happened, here to share with you:
- We committed and delivered on the dependency for JSM Approvals - Group Pickers, yay
- Also, Automation platform experiences a couple of months ago
You should now be able to rename groups that have those dependencies and not break those experiences, if that isn't the case, please contact us at our support.atlassian.com channel.
Bonus: Last time I mentioned we would deliver group renames to customers that are not yet in the new administration experience, that is done! We are working internally to update ID-8234 that was created to track that impact and helped us commit to doing it!
As always, thank you & we've never been so close!
RODRIGO BECKER
Product Lead, Atlassian Guard
Atlassian Update – 30 October 2024 Hi everyone, Sorry for the radio silence, but good things still happened, here to share with you: We committed and delivered on the dependency for JSM Approvals - Group Pickers , yay Also, Automation platform experiences a couple of months ago You should now be able to rename groups that have those dependencies and not break those experiences, if that isn't the case, please contact us at our support.atlassian.com channel. Bonus: Last time I mentioned we would deliver group renames to customers that are not yet in the new administration experience, that is done! We are working internally to update ID-8234 that was created to track that impact and helped us commit to doing it! As always, thank you & we've never been so close! RODRIGO BECKER Product Lead, Atlassian Guard -
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
-
- In Progress
- is related to
-
JRACLOUD-83598 Announcements dependency for Group rename
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-