The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Great article, very easy to understand the changes coming and I like the new look of the group and user management.
Is it possible to start to see the changes before June (as an existing customer)?
Great enhancements , really like this centralized user administration.
Wanted to ask if if I can have multiple instance for one product aiming to have some employees like standard and some premium for jira software for example not having all of them standard or premium
Hi @Kieren are you planing any changes on the Landing product setting? Currently it is either Jira or Confluence across all the users and groups which is not very convenient for our use cases. I need the new users from Group 1 to land on Jira and users from group 2 to land on Confluence. As a digital agency we run multiple projects with various user groups that include customers, employees, and vendors. For the new project I might need employees and vendors to land on Jira, but customers to land on Confluence. It would be really helpful if I can specify this on the group level when setting up the new user group.
@Kieren you should address Bitbucket directly in the article. As it is right now, it's somewhat confusing as the expectation (and concern) that I had was that it'd unify Bitbucket somehow. The details that I was interested in (i.e. that Bitbucket wasn't yet affected, despite the prominent messaging about "unification") was not at all visible until you manually click through the second page of comments (which aren't fully visible/searchable using CTRL+F because it's broken up).
Thanks for the feedback @Patrick Nelson, I've updated the article to include that.
@Kieren Can I change group names (not descriptions) when the change occurs?
@Kieren - the article doesn't seem to mention Bitbucket yet, have you published the edit yet? Just checking :)
Will this feature be extended to provide the ability to manage individual user access to third-party apps?
Pourquoi Juin 2021 pour les membres déjà dans le système, quand même loin si déjà dispo pour les nouveaux clients &
Will be great if you add official user management portal for vacations, day offs, sick leave etc. And with integration with time management or time tracking.
Looks good, looking forward for the upgrade!
On one hand I am glad that the user and admin management is getting an overhaul, but this has created a real problem for us at the moment.
Upon being forced to migrate all our 7 users (under a 10 license agreement) from Statuspage.io over to our Atlassian instance, our admins are now included as users of Statuspage and any time I want to add an admin, I cannot without increasing our license for Statuspage.
This has now triggered an entire review of our admin permissions... not very happy with this at all. I am optimistic that the new Admin Management changes above are going to help me resolve this issue. Time will tell I guess
Nice work, Atlassian and thanks for posting Kieren! Love the new UI ... 2 questions - would this be rolled out on cloud for everyone by June or will it be opt-in-able - ie. can we opt to see it before it is rolled out to us? And what is the plan on managing users, groups, products and interactions inbetween these via the API. If we have a connect app - when can we manage staff on and off boarding via the App, etc? Thank you
Hi @Kieren ,
In your answer of January to a question regarding "Site Admin" effects, you mention that a post will be published later.
As this change will happens in two weeks, can you please specify when the post will be available for us to take actions if needed ? We receive a lot of question about this and impacts and we are not able to answer yet.
@Kieren , it would be great to have a webinar to cover this change and allow for Q&A.
Hi Atlassian Team, in an email about this change back in January that linked to this article, we were informed that an upcoming change on June 1st would mean that site admins would lose user management privileges:
However, it appears that site admins for our organization still have user management privileges. Am I misunderstanding the implications of the change, or has the change date been delayed?
@Fabrice Huart , @Yatish Madhav , @lewisgn
The rollout was delayed, we'll send an email to customers a month before we intend to migrate them to the new experience.
Right now, we intend to migrate the first customers on 22nd September 2021, through to about December 2021.
@Jack Brickey Great idea! I'll organise something with the next blog post about the new admin roles.
Me gusta mucho
Will this / new admin roles change any API's and to test new API's will you need to make and new org?
Thank you for this information. Looks to be more intuitive.
How can I try this out to provide feedback without rolling my site over to the new product. I want the ability to try it using the Jira Labs option so I can give feedback but be able to go back if it doesn't work.
Do you understand your customer base at all? You're going to give this to new users who don't currently have a complex system set up and get their feedback. How are they going to encounter the problems your existing base will see? How do I get this tied to Jira Labs so I can look at it before it is thrust upon me.
Will site admins just lose access at anytime?
WIll they get auto added to the new roles?
Will they need to become ORG admins just so that don't lose access at an random time?
And 1 month IN DEC IS BAD. Unless users keep the same access.
Please add Bitbucket to Atlassian Admin.
6 accepted answers
51 total posts
Hi Community! Thank you to all who joined our ongoing monthly Atlassian Access demo! We have an engaging group of attendees who asked many great questions. I’ll share a recap of frequently ask...