You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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.