Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,551,690
Community Members
 
Community Events
184
Community Groups

Incluse issues from different project in release

Frank J. Øynes
Frank J. Øynes Mar 19, 2019

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?

Answer
Watch
Like Be the first to like this
296 views

2 answers

0 votes
Tarun Sapra
Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Mar 19, 2019

Hello @Frank J. Øynes 

As @Walter Buggenhout _ACA IT_ 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.

Reply
0 votes
Walter Buggenhout _ACA IT_
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Mar 19, 2019

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. 

Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced Roadmaps
TAGS
AUG Leaders

Atlassian Community Events

See all events