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
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When you have a work stream that manages perpetual streams of work (nested/organized by client), using EPICS that remain open, with linked stories that get executed (open/resolved/closed) seems to skew reporting (time to close, avg time in status, etc.). How do we classify this work, so that we have a history by client of all work requests, features, etc that get executed. Using tags and labels seems to classify and group the work, but then you can't see the details and history - that only allows you to pull data by tag/label - we need to have all work (and the history) roll up to a level ...so is this best achieved using Initiatives, or Programs vs. trying to keep Epics open indefinitely? Please advise.
Hi @Kelly Jones,
To help clarify the difference between programs and initiatives:
It sounds like using initiatives may suit your needs better. We have our documentation available here: https://confluence.atlassian.com/jiraportfolioserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html . I'm not 100% sure if this will solve all your needs, but let me know if you think this will work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.