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

Does Jira support the concept of multiple parent links or upstreams like JAMA does?

We have been using both Jira and JAMA in our company and in JAMA we were using the concept of multiple "upstreams" This is very important as we can have the same story enabling multiple Epics. We were able to do this easily in JAMA as there were no limitations on how many upstreams or downstreams links we can have. Does that concept exist in Jira? I scoured through the community and did not find anything favorable. How have people been doing this?


Plain Jira Core does not have a way to do this, but when you add Portfolio to it, then yes, you get all the initiative/theme/your-layer functions on top.  (And Align - that handles it even better)

Like Tom Kakanowski likes this

Thanks for that, its an avenue I will investigate!

Nic, yes I am using Portfolio as well. Although I still see a fixed limitation of one. For example I can use the parent link and there can only be 1 value there. In Jama, I am able to have more than 1 parent for a given child. Even if I use the Epic Link, there also it is 1.


I tried to use Initiatives with portfolio and that works fine for initiatives having multiple Epic.. I am still unable to have 1 Epic have 2 initiative.. Essentially the concept of how do I get more than 1 parent linkage?

You wouldn't expect Epics to belong to many initiatives - look at splitting them up if you think you need this.  (Dependencies are a different story of course)

Yes we are doing that right now, that is how we are working around it. Although it does cause a proliferations of Epics in the system. Also even more important is the ability to have multiple parents for the stories.. 

Our use case is that we have a team that works on embedded software, a team that works on hardware tools and a team that works on software developer tools. All 3 components have to meet at a union for a full solution to be possible. What is going on today is since we can only have 1 Epic link, the first one to link to the story wins. This makes it harder to track as some of the stories are cross linked from the teams. In a small company this is very simple to do, although in a big company like ours it needs a lot of co-ordination.

In Jama we solved this by having multiple parents to the same "stories" so this way each parent can track the state.. Does a concept as such exist in Jira/Portfolio?

Like Bennett Maina likes this


Log in or Sign up to comment
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,555 views 25 18
Read article

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