So I'm a Jira admin, helping advise different departments on their Jira implementation. In keeping with Agile principles I'm happy for teams to organically find workflows that work for them and customise accordingly. Recently, one team got started with Jira and opened up an interesting discussion.
Is it better to create separate projects for each release, or separate releases within each project?
My gut feeling is to just set the fix version for each release, and create a 'release' when finished but the team wanted to go for separate projects for each release, stating the following reasons...
Thoughts?
Definitely in this case 1 project with multiple releases makes sense. This why fix versions are there in Jira.
I think it is more of a case of training the users about filters, issue navigator, dashboards and reports. Since you mentioned agile. Also educating them on using epics, labels, boards with relevant issues only and utilising these capabilities to the fullest of Jira.
Ravi
I concur with @Ravi Sagar _Sparxsys_
It's important users learn how Jira works - it is a flexible system and teams should use it to suit their ways of working. But, there can be pitfalls to some approaches.
In the instance you've described, I think it makes sense to have one project assuming this is one product to be delivered or one team delivering consistently. This is because:
The concerns they've mentioned can be handled through some knowledge of the boards and issue filters - for example:
^ Easily manageable and less convoluted than having multiple projects.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.