You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Similar to it is in Jira Software where you can create tasks/US under a project and optionally nested under an Epic, I'd like to create in Advanced Roadmaps US/Tasks under an Initiative, but without linking them to an Epic.
In the end, the objective is that I, as a project manager, can create/plan tasks under initiatives that at a later stage each development team can assign to their own Epic. This considering that the current hierarchy level I have configured is Initiative - Epic - Task/US
Is this possible somehow?
Can't be done and I'm not convinced it would be a good idea or one Atlassian are likely to pursue.
So, in your case I would create a "Project Plan" Epic (or whatever you want to call it) and create your plan tasks in it. From there teams can either;
@Joe Lagana-Jackson if you have infrastructure or Tech Debt work that needs to occur as part of the DOD of an Initiative, then it is part of the solution and should be as transparent as any other component of the Initiative. Incorporate into existing Epics, or create those "tech debt" or "infrastructure" ones. #tellitlikeitis
@Curt Holley Yep, that's what we try to do. I usually get pushback because folks get bogged down if something goes across multiple epics. I don't see an issue with having "orphan" task. To me, this doesn't make it invisible in the plan, it just means it's not associated to an epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fair enough @Joe Lagana-Jackson
What I've seen done is just using a link type (say dependency) direct to the Initiative from the misc stories.
Just a thought.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would love this feature as well for a different reason. Many times there is work in an initiative that doesn't really fall under an Epic, but supports all epics or is cleanup work.
Right now, we have to create epics like "tech debt" or "infrastructure", and we prefer to keep our epics customer facing in nature, and these above epics are more like categories than anything truly useful from my perspective.
I would love it if we could skip a level in the hierarchy. I don't believe there's a way to do this today.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can issue links to create your own hierarchy.
To visualize the hierarchy based on the issue links, we have created an app to track the progress at each hierarchy level,
Agile Tools - Epic Tree, Links Tree and Time in Status
Key features of Links Hierarchy:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.