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

Share an issue between two Projects Backlog

Moria

Hi all,

I would like to submit an issue that should be handled by two different teams that work on different projects. Both teams should see the issue and update it accordingly in their board/sprint.

I have tried tweaking with custom fields layout and so, but so far I did not find any appropriate solution for it.

Can you please suggest a solution?

Thanks!

Accepted answers

Mohamed BENZIANE

You could copy the issue in each project and use a link between them.

If you work with only one issue for both board, the issue can only belong to one sprint at the time.

All comments

Mohamed BENZIANE

You could copy the issue in each project and use a link between them.

If you work with only one issue for both board, the issue can only belong to one sprint at the time.

Paul O_qqk8km

An issue will only exist in one project.

However, the boards and backlogs teams look at are built from filter queries which can span projects so you can show a single issue in multiple backlogs. (You can't however, have a single issue in two active sprints.)

A typical board is built from a filter like:

project = ABC ORDER BY Rank ASC

This filter can be changed by accessing the board settings (using the ... menu on the top right of the board and changing the filter)

There are many ways to adjust the filter to include your issue. One simple approach would be for you to label the issue with the teams you wish to see the issue and then change the filter for each team's board to

project = <project key> OR Labels in (<TEAM_NAME>) ORDER BY Rank ASC

The above query will include ALL issues that are in whatever project the team usually works on AND any issues that are labelled with the team's name even if from a different project.

Moria

What would you say about this procedure to share an issue between two projects:

Create an issue in project A
Clone issue
Move the cloned issue to project B
Link "cloned" Issue > relates to > project A
Link "original" Issue > relates to > project B

Thank you

Mohamed BENZIANE

Yes perfect, i will just do the 4 steps you don't need the fifth step, because you just need to link the issue one time.

Moria

Yes! Thank you friend

Moria

Thank you for the explanation - but this option requires modifying the filter on both sides and I was looking for a simple follow solution

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