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
We have a use case where we have tasks come in related to one epic but are effectively an interrupt, so we use a second epic to identify interrupt issues. Would there be a more effective way to identify interrupts and report on these without having to duplicate tasks?
I have run labels on issues that are interrupts (such as "Sprint-22-OutsideWork"), keeping these issues outside of the running sprint. I then run a filter on a dashboard to roll up all of these interrupt issues during reviews. It helps preserve the sprint from massive scope change but also provides visibility to the org that the team is getting pulled off the sprint goal.
Hello, there is a real need around this notion the same improvement that needs to appear in different stories, just because we are working on different stories in parallel and they share some basic functions
Relates to is not enough, because you can't see the evolution in a good way. Epic provides such a view.
Hi @Dan Osborn ,
Currently you cannot link issue to multiple epics via Epic Link due scrum board constrains as it may deviate your report results.
As alternative you can link issue with more epics with issue linking feature in Jira. Also if you can create duplicate issues and link them to individual epics if you looking to get more accurate reports for your epics.