Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

We have a few questions around Jira Next-Gen.


1. If a project owner leaves the company and there are no other admins on the project, will a global administrator be able to view and take ownership of the project?

2. If admins are added to new projects in Next-Gen, is there a cost impact for that user role?

3. We do not want users to have the ability to invite people to projects that do not work at our company. Currently this is open, how do you lock this down?

4. Will the capability to migrate Classic projects to Next-Gen ever be available? 

1 answer

1 vote
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 08, 2018

Hello Shanon,

Please, allow me to address some of your points:

1 - Yes, a site Administrator is able to edit which users should be able to access the project or change the project lead even if he is not added to any of the project roles and can't even access it.

To do this, the site administrator must navigate to the projects page > find the project you would like to change > Click on the three dots icon > Project Settings

There a menu called "People" that he will be able to change the details you mentioned.

2 - No, the cost for any users on JIRA is based on Application Accesses, which is counted for any user that can access JIRA application. The cost will be the same for simple users or site-admins

3 - You can configure a next-gen project as private by navigating to the project > Project Settings > Details > Change the field Access to Private

This will block any users that are not administrators on that projects from inviting new users

4 - Actually, you already can migrate issues from Classic projects to Next-gen projects as you need, although you have some limitations.

Please, check the documentation below to know what are those limitations:

Migrate between next-gen and classic projects

Hello and thank you for your respond.  I have one follow up question below:


1- All of our admins are unable to even view the projects that have been created by others?  Is there another setting we are missing in order to view all of the Next-Gen projects?  


Thank You,



And apologies, one other follow up @Petter Gonçalves, is there somewhere we can globally set all projects to only be shareable to other users in our domain (no one outside of our company)?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events