You're processes around JIRA projects?

[Bart Meerveld]

Hey guys,

We've been using JIRA for over a year now at our company. I've entered the company 3 months ago as JIRA administrator. I was completely new to JIRA when i started but i feel like i've set it up pretty nicely now. To keep it that way in the future i was wondering; what is your current process for a new project request? I feel like there are currently a lot of requests from all departments in the office for new projects that are incomplete, unauthorized or just completely unnecessary. So my questions:

• At your company, who can request a new project?
• What info do you request at minimum?
• What are your minimal requirements for a new project?
• When you do set up a new project, do you have something like a checklist you follow?

[Vasiliy Zverev]

We request:

• Name
• Description (optional)
• project lead
• category

We also use buillt-in script "copy project" provided Script Runner plugin. All schemas are the same into project category.

[Bart Meerveld]

So you decide what their workflow is? And their issuetypes and such?

[Vasiliy Zverev]

We have several project categories and all projects in this has the same schemes (workflow, issue types and ets) and fillig of project roles. When we copy project all schemas and roles are copied too. Now we have 1000+ projects.

[Vasiliy Zverev]

I would reccomed to create some project with predefined schemas and base fill of project roles. And then only copy it. It is bad idea to have a lot of project with different schemas.

[Nic Brough -Adaptavist-]

I'd also say we tend to have a "JIRA project" for handling these requests alongside any other JIRA support work that might need to go to your admins.