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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Next-Gen project per defult on private? Edited

At the moment every single "next generation" project is per default an "open" project. Everybody who has access on jira can see and edit this project. How can i avoid for example external user can see every single next gen project? External means members of an external company who has access to jira, but should only see projects they are relating to them. 

Yes an admin could change the project permission for every single one to private but this take too much time.

For the old projects you could use a permission schema per default to avoid this behavior.

1 answer

0 votes
Jack Community Leader May 09, 2019

when you create the new project it allows you to select the permissions. you cannot change the default however.

Ok, the problem is the most people who creates new gen project dont know anything about permissions or they dont think about it.

If you create an old project it takes the permissions you have(as admin) set up before per default. So every new project(without new gen) has it right permissions.

Very sad it doenst work.

Jack Community Leader May 10, 2019

i don't understand. when i create a NG project it clearly prompts for how 'open' or 'private' you want the project to be.

Yes, the promt works just fine. The problem is, the default setting should be the most  "safe" option. 

The problem is, we have several  external customers whom we grant access to their projects. And we have users.

So if my boss creates a new project like "Super sekrit project for company C" and hammers the blue button (because that's what most users do), it will be visible for every customer, because he forgot to change it from open to private.

I can't babysit Jira 24/7.

And no, apparently you are not able to restrict certain users to one project only, because the user "anyone with access to xyz" user who is added to each open project can't be edited and overwrites every restriction you try to set .

Like Marco Betzner likes this
Jack Community Leader May 19, 2019

You might want to provide feedback to Atlassian via the feedback link. 

Feedback location appears to be here and so far Atlassian seems unmoved:
https://jira.atlassian.com/browse/JSWCLOUD-17234

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

781 views 2 21
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you