When to create a new JIRA Project dilemma?

Hi Gang,

I am racking my brains as to if we are using our JIRA system in a sensible way or not.  Currently, whenever we have a new engineering project (that is run under our agile process) we create a whole new project in JIRA that contains all of that projects epics, storeys and tasks.  That JIRA project then encapsulates everything to do with that project, and then when the project is finished, anything left over is either closed off as not being done, or move in to another project which is used for released versions of the product (i.e. customer support issues, none project related bugs, etc) as our releases are done in a waterfall process and support issues requires a different work flow to agile projects.

This process seems to work fine, however after reading the hardware sizing documentation for the server running JIRA and how the number of projects the JIRA affects the spec, it is making me wonder as to if we are going to start to run in to trouble after we have run 100 or so projects (probably not for a while yet).

So, am I doing it wrong?

Should we just have the one agile JIRA project that is used for all our agile project work, and have a field that can be used to assign a JIRA item to a specific dev project code?  Can you run multiple sprints at the same time under JIRA agile and not faff up the reporting of those sprints/separate projects given that they would all be under one JIRA project?

Thoughts on my dilemma would be much appreciated!

Thanks

2 answers

1 accepted

 

Should we just have the one agile JIRA project that is used for all our agile project work, and have a field that can be used to assign a JIRA item to a specific dev project code?  

 

  • Whether you create new projects for all your new work or not, for me it always come back to traceability and ease of use. If you think reporting and tracking will be better this way, stay on it. If you want to use a single JIRA Project, you may use "Components" to categorize the work (Database, FrontEnd, Infra etc...). In our use, One Product = One JIRA Project.

 

Can you run multiple sprints at the same time under JIRA agile and not faff up the reporting of those sprints/separate projects given that they would all be under one JIRA project?

 

How big is your hardware? The number of JIRA Projects/Issues should not affect that much (I have 1,200 Projects, 600,000k issues) and everything still runs smoothly. Read JIRA 5 Performance Secrets article.

Thanks for your answer.  This gives me some food for thought!  Cheers

You are most welcome, cheers! :)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,755 views 11 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot