Criterias one JIRA Project vs many JIRA Project within a Company

Hi all,

currently we discuss how to implement JIRA within our Company.

The main question is, should we set up one company wide Project or many(every Division/Business Unti)JIRA Projects? What are the criteries for helping us to find the correct solution?

Thanks in advance Fabio

1 answer

1 accepted

Accepted Answer
0 votes

Hi Fabio

The governing rule we use to decide whether a new project is required or not is how the releases are going to be managed.

If all issues logged in the project will have a common release cycle then it justifies one project. However, if they are supposed to folow multiple release cycles then we log them under different projects. We want to be able to track affect versions and fix versions in future and thats the reason we follow this approach,

Rahul

Thank you Rahul, to be sure that I have understand you correctly. If we have n-applications with different release cycles with low correlations, we have to set-up n-Projects?

Fabio

Yes, you are correct. If there are two issues which would follow their unique release cycle then both need to be in separate projects. At least thats what we follow.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

45 views 0 2
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