Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I manage Multiple site code delivery against a single group of issues?

My application/organization is migrating to MyJira and we are trying to figure out how to organize our Project.

We have a single CodeBase of Delivery across 3 delivery sites.  Our release management team has requested that we link our Issues to an Epic that will have a defined Fix Version that will be used for them to track what is included in our biweekly release to Production.


Since Jira only allows an issue to be linked to a single epic we are not sure how we will be able to organize our items for release management without having to first duplicate our Issues for each of the different epics.


2 answers

1 accepted

1 vote
Answer accepted

Hey @Liam Gillen  - Epics don't have to live in the same Jira Projects as all the work that makes them up (though that is the default). When scaling it's common to have a single central "Roadmap" or similar style project where cross-team epics (and other cross-team items - for example requirements being shaped where the team to engage isn't known yet) are held. 

For your scenario of Release management, the team might find that having a shared release calendar in Confluence or similar might be a better solution though. Normally Epics are literally " big stories" so you don't want one sitting open for ages just for tracking. Using the Fix Versions properly and some Release Note conventions is a good approach I'd say - I've seen good outcomes from having a special /RELEASE project where custom issue types are the Release notes and you link those to all the tickets included, pop in the release instructions etc. 

Thanks for the feedback, I will discuss this with my larger team and Release Mgmt and Tools Team partners!

Like Kit Friend likes this
0 votes

In addition to what @Kit Friend suggests, there are also options in the Atlassian Marketplace to add functionality to Jira and for example superpower your epics, create more complex issue hierarchies, or adopt cross-project release timelines. But the possible apps depend on your hosting type. @Liam Gillen are you on Cloud or on prem?

Thanks we are exploring options, but with a Giant company these things are not always possible.  Unsure, but would assume given our overall direction that we are in the Cloud.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you