Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,459,450
Community Members
 
Community Events
176
Community Groups

Support for dependencies between initiatives

Hi guys,

Currently having a look at JIRA Portfolio to determine whether it meets our needs.  One of the questions I've come across is that currently dependencies can only be set between Epics and Stories, not Initiatives.  This does not suit our real world scenarios.  Our initiatives fall into several areas, data warehousing, report generation and product development being some of the main ones.  We have dependencies between all of these which we can currently not capture.  These cannot be created as epics as they have different business drivers.  So the question is why not have dependencies between initiatives?

Rob

2 answers

Thanks for the prompt reply, Martin.

I was afraid that was going to be the answer smile

Cheers

Rob

0 votes

Hey Rob, we originally haven't built dependencies for initiatives as initiatives were seen as grouping elements rather than work items like epics and stories. This is why also it is not possible to add an estimate to an initiative directly while it does not have child epics, whilst the same is possible for an epic. It's been an implementation choice that constrains us now, and requires more significant restructuring in the backend to enable dependencies on that level too. We'll change that down the road, but currently the only option is really to create the dependencies between all the child epics. Best, Martin (Product Manager for JIRA Portfolio) 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events