nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Criterias one JIRA Project vs many JIRA Project within a Company

Fabio Attili

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

Accepted answers

Rahul Aich [Nagra]

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

All comments

Rahul Aich [Nagra]

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.

Rahul

Fabio Attili

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

Rahul Aich [Nagra]

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.