Best Practice for JIRA Project Setup

[Alyssa Todd]

In our organization, we can only have one project for our program work. We have several projects that have similar requirements (ex: needing to track an owner to an asset is a requirement that spans several projects). We also have stakeholders that span these projects as well, and should have visibility into the work. What would be the best way to set up our single Jira project that contains several projects with interdependencies?

[John Funk · Accepted solution]

Hi Alyssa - Welcome to the Atlassian Community!

You might try setting up the single project and then create the other "projects" as Epics under that single project. Then you can link the Epics together as needed. 

[Paul TEODORESCU]

hi @John Funk , how would you recommend to setup different ITIL practices (incident, problem, change, etc.)? As Epics?

I am troubled by the fact that all ITIL practices are set up in one project, as such a complexity in managing SLAs and mandatory fields in ITIL worker form.

[John Funk]

In those cases you might want to have separate projects. Totally up to you. 

[Joe Pitt]

You can't have projects within projects.  If you aren't using the component field that would be a way to flag different areas of the project. If you are create a select custom field with the different areas. Either way, make the field required upon creation.

[Lucas Lombardo]

Hello,
Currently I work with different Jira projects (depending on product) and I created a specific board to follow interconnected subjects. All issues with the label "label-example" appear on this board, no matter the project. Of course users should have the good rights on projects to see the issue on the global board.