Not with epic link, but you could use a linked issue.
Or you could use components... depends on why you have the story in more than one epic.
I hope it helps..
Regards. Marce
You are genius!!!! saved my life!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The visibility on the progress through an epic, or 'how much longer will this take?' is brought about by breaking that Epic down into smaller bite-sized chunks so the Epic is slowly eaten, one bite at a time and we can measure that progress.
So in that sense, Epic 1 has a set of Work Items (issues) that are its 'bites', and Epic 2 has a different set.
and the reporting relies on that.
But I get that there may be a sense of 'Hey, I just realised that this work also contributes to that 2nd Epic over there.'
All I can think of is:
could that work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there any plugin in the marketplace that would allow us to do this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Thanks,
Avinash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.