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

Incluse issues from different project in release

Frank J. Øynes

Given a project A with several coming releases defined.
And - given a support project B which is fixing a bug in a product belonging to the release plan of A.

Can I add a relevant bug-issue from project B as part of my release in project A?
Now I am cloning the issue, but this causes extra work when updating and closing issues. Is it possible to just link/refer to the issue in project B so that updating will become visible in both projects, and still part of the release plan?

Comments

Walter Buggenhout

Hi @Frank J. Øynes,

Your releases (or fix versions) are project specific in Jira. So no, it is not possible to associate issues from project B to a fix version of project A.

Tarun Sapra

Hello @Frank J. Øynes

As @Walter Buggenhout already mentioned that the fixVersions (releases) are project specific in Jira. One of way you can try to circumvent this issue is create a Kanban board and move the issues to done column. And then from the Board make the release of the issues in done column. In this way the fixVersion(release version) should get added to all projects to which the issues in done column belong.