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.
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events