-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
1
-
I would like to have the ability to grant permissions to users to create projects using shared configurations (i.e. company-managed (formerly classic) Projects). Currently the only way to do that is to grant Administer Jira permissions. This level of access is excessive.
This would allow for one central Jira Admin to create and manage enterprise approved workflows, permission schemes, issue types etc..., but would allow multiple people to create new projects using the approved enterprise configurations.
Currently the permissions are not granular enough to allow this, and anyone who can create a company-managed (formerly classic) project, can also create workflows, notification schemes etc...
- duplicates
-
- Gathering Interest
- is related to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWCLOUD-17242] I would like to have a permission that grants a "Create company-managed Project Permission", without having to grant "Administer Jira (global permission)"
I believe this issue is a duplicate of JRACLOUD-1431 – Create a separate permission for Create New project..
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!
Hi Merit, Jason & Kevin
In case you are up for a cost-effective third party solution that's hosted by Atlassian to allow non-admins to create company managed projects.
Project Templates for Jira offers an efficient way to design custom project templates based on existing projects or Jira's built-in templates within a Jira lookalike user interface.
- Customize the templates configuration to meet your unique requirements
- Give non-admins template specific project creation power
- Customize the UX & information displayed to non-admins
- Clone project versions, components and project role actors
- Avoid the technical debt of unnecessary created Jira schemes/configurations
The app is built on Forge with no data egress, no sensible information stored and completely hosted in Atlassian's cloud infrastructure.
Please let our support know if you have any questions.
If the point of using company managed is to ensure consistency and features between projects, then having system admins create the templates for these project makes sense. But once the templates exist, PMs should be able to create new projects using those templates. This is how every other system works. We need another permission for create company managed project.
Please make clear that this issue also pertains to Business Projects, not just "Classic Projects". You have released a number of new and interesting templates as part of Jira Work Management but it doesn't make sense for us to give golden keys to our whole Jira instance to the business users who would benefit from these templates. Please fix this issue 
As I did not receive any responses to this comment I am closing this ticket.
If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.