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; } } }

Linking projects

Mauro Cortesi

Hi there..

I'm new on Jira....trying to discover how to implement it with the less regret in the future...

For now, I'm stuck with this...

Is there any way to link a project to another project?

Something like parent->child....

We've projects of different products, with diferent issues, versions, etc.......but they can be related to each other.

The only I look for is to know for a project, if it's related to another...... or for a particular project, get a list of his associated.

First thought was create as many components as 'child projects', still have associated issues (to a component)....but lose the release versions for that components/projects......right?

Is there a limit for number of projects?, components?

Thanks,

Accepted answers

All comments

Tarun Sapra

There is no limit on project and components. In JIRA you can't link projects, thus the best approach is to have components for smaller initiatives, and create a board (Scrum/kanban) wherein you fetch issues from multiple components.

What do you mean by "but lose the release versions for that components/projects......right?"

As you can have per component boards and make releases exclusively for issues pertaining to that board.

Nic Brough -Adaptavist-

Project categories can help you group your projects together, but there's no real "link"

Blair Rodgers

I also need to be able to link projects, one master project, with many smaller projects that must have separate Jira numbers (prefix), project names but ultimately have a way of linking back to show full view of the entire project and the progress of all of it's mini projects below.

An umbrella project of sorts, with many smaller projects that make up the whole. Lots of moving parts

Stacey Ward

Hi @Nic Brough -Adaptavist- , is there any update since 2016 on @Blair Rodgers comment below?

Any other community leaders to assist?

Thanks!

Blair Rodgers

Hummmm, not ideal. For instance, I’m currently on a project that has 18 seperate mini (For lack of a better word) projects that all run concurrently and not having the ability to make one master and multiple mini projects that link back to the master, it gets very messy and I cannot report easily on the progress of each part of the entire project.

Richard Cross

The best way to do this is via Portfolio for Jira, which is now built-in to Jira and called "Advanced Roadmaps".

https://www.atlassian.com/software/jira/features/roadmaps

This allows you to organise your projects into a Plan, and those Plans into a Program.

The advice from Atlassian is to create another project in your plan to hold cross-project "Initiatives" that (in the Plan), serve as a hierarchy above Epics.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud