My company has a large number of projects in jira. Regularly, new projects have to be created. In order to restrict this ability not only to one or two administrators, lots of people are made jira-administrator. Thereby giving them access to much more capabilities than they should have. Like adding groups and users and changing permissions.
Is it possible to give only a restricted set of administrator rights to a users? So that he or she basically only can add and delete projects?
thanks in advance, Ruud
Not yet. There's four layers of rights, and no granularity within the rights they confer - if you're in a layer that can create projects, you can also delete them, hack custom fields, fiddle with workflows and so-on.
Atlassian have had this one logged for a while, and have said that they are now actively working on it, and according to https://jira.atlassian.com/browse/JRA-3156, we should see something in the next 6 months.
But for now, no, you're stuck. There are some inventive workarounds using code and remote scripting, but they all need you to set up a full admin user and pretend to be that user.
If you also use Confluence, then you can follow these instructions:
Without Confluence it would be a significantly more difficult. You could setup a project restricted to users that need to do create projects. For each project to create, they would need to create an issue, specify some specific custom fields with the parameters of the create and then do a "Create project" workflow transition. The transition would use CLI Plugin for JIRA to run the create project action bringing in the custom field values for the create parameters (this part could probably be done by a script runner post function as well). The downside of this approach is there is no capability to report on errors from a post function without access to the jira log.
You might want to take a look at our add-ons Project Creator for JIRA ( https://marketplace.atlassian.com/plugins/com.wittified.jira.project-creator). It allows you to define a set of "templates" for projects that a subset of your users can create projects from. This basically allows you to focus on the configuration of your JIRA instance and not be interuppted by creating every project (and instead let the person needing to create the project to create it ).
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs