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

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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.




Epics are further down in the listPortissue2.jpg

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?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events