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?
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)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs