Next-Gen project per defult on private?

Question

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.

Miles Kafka · Answer

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

Jack Brickey · Answer

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

Anna_kh87yx · Answer

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 .