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

1 Issue in 2 Projects

Juan Du Toit

We 1 project that needs work done from more than 1 team. So in the main project, all the stories will be created and then moved to whatever team will be doing the work.

The PM still needs to see in what state the main project is. Is it all possible in JIRA 5 to have 1 issue cloned to another project in such a way that any changes done on either issue will reflect on both?

Thanks Guys,

Juan

Accepted answers

Nic Brough -Adaptavist-

No. An issue belongs to a single project.

The best you can do is duplicate the issue and then link it to the original, then you'll need to find or write something to keep the two in synch.

All comments

Nic Brough -Adaptavist-

No. An issue belongs to a single project.

The best you can do is duplicate the issue and then link it to the original, then you'll need to find or write something to keep the two in synch.

Juan Du Toit

Jip....thats what I thought.

Is there a plugin that can do this, that you are aware of?

Nic Brough -Adaptavist-

Not that I know of.

Most places don't see the point of having duplicates. If they really need a duplicate issue in another project, they tend to create a "stub" and link it to the original with a message saying "go look over there". Problem with trying to keep two issues in sync is that you have to code for every type of change - it gets long and messy quickly.

Juan Du Toit

Thanks Nic

Welcome!

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

Quick Links

Find more posts tagged with

jira