Kudos (beta program)
You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupIt's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Epics are not associated to initiatives when it comes to prioritization -impacts forecast capability
We use the hierarchy of Initiatives/Epics/Stories/Subtasks
In portfolio we look at Initiatives and Epics for forecasting. We are experiencing some initiatives that are going out past 1 year, even though the estimates are only 200 hours of work. What we realized because of someone else that experienced this previously was that even though in the view, the Epics appeared to be WITHIN the initiative, they were actually way down on the list of priorities when you just looked at Epics. You can't see this natively in the tool because you cannot see Epic priority number.
Initiative
Epics are further down in the list
The capability to find and easily move all of these items is very cumbersome and could create further issues. Anyone else experiencing this lack of relationship?