Is there a way to let users create projects?

[nilo soto]

New to Jira and It doesn't seem like there is a way to customize Global Permissions out of the box. Am I missing something or is it that Jira/System Administrators are the only ones to be able to create projects. I have a few users that will need to create software projects from time to time and would be more convenient to allow them to do so.

Thanks

Nilo

[Clark Everson · Accepted solution]

@nilo soto 

Out of the box no there isn't. You also want to be careful as too many projects can slow down an instance so you would want to review Atlassian's sizing guides for your instance. As new projects add a lot of schemes there are a lot of different objects that when users create projects and it isn't kept track of, can lead to very quick undesirable instance growth, and performance impacts on all users. Especially in server.

https://confluence.atlassian.com/jirakb/jira-server-sizing-guide-975033809.html

If you aren't concerned with performance (though I would advise against that) you can do this via plugins, either using something like ScriptRunner:https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?tab=overview&hosting=server

Or Delegated Project Creator: https://marketplace.atlassian.com/apps/1211157/delegated-project-creator-for-jira?hosting=server&tab=overview

Best,
Clark

[nilo soto]

Thank You

[Joe Pitt]

It may be more convenient, but it could become a mess. 

 I STRONGLY suggest you treat JIRA like a production system, put it under change control (CR), and track all requests for any updates, especially new projects, new custom fields, changes in any of the schemes, etc. That way at least the reporter will know when the actions happen and you'll have a audit trail. I've worked many similar tools to JIRA and too many times no one knows anything about why they are configured why they are because there is no requirements or CR. Things are just done based on emails that have disappeared and hallway or lunch conversations.  

 If you don't already have a separate change control tool create a JIRA project. I use a basic workflow with a few custom issue types:

 Custom field: with a select list of create, update. The description would be to create a new field or modify a current select list, buttons, etc. of a current one

 Create Project: I would have text fields for issue types, custom fields, select list/values, per issue types

New Issue Type: description would include all fields and workflow desired.

Workflow: Select list of Create, update, delete. Description of what needed.

Other: Select list of Notification Scheme, permission scheme, field configuration, other

 This should get you started. If you aren't familiar with your CR process there should be a configuration management person to talk to.

 The goal is to manage what you do and be able to track who asked for what. For instance, if someone wants a new custom field you want to check to see if there already is one you can use that they don't know about. JIRA will let you have multiple custom fields with the same name, which will just confuse you.

[nilo soto]

I agree but MGMT keeps asking

[Joe Pitt]

At one place they didn't like fields not being displayed if they were empty and forced me to put a default value. After about 2 months I showed them more than 80% of the users never updated the TBD to a real value. We got rid of default values.