Is there any way to leverage the behavior of epics across multiple workflows that support different teams?
My team is using a custom workflow different than the rest of the company. I'd like my team and our board to support epics. I'm specifically after the additional nesting behavior as well as various epic tracking and reporting mechanisms.
It seems as though there is only one definition of epic for the entire company. I can't change the behavior of epics just for my team. Things I've considered:
My team currently cannot see epics on our board because they have a different workflow. I'm trying to avoid adding a new workflow to our team because the extra issue types create confusion (especially when ticket are created with types that don't jive with our board). My impression is this limitation pushing things into the "can't be done" category.
I've searched in various ways but haven't found this asked before.
Thanks for reading and considering.
Hi Ravi. The end goal is for the team to be able to run agile with a kanban board - this means having our own workflow so we can adjust columns in a team based kanban like manner.
For Epics in particular, the need is for a deeper hierarchy. Without them we have story->subtask instead of epic->story->subtask. By nesting, I was simply referring to the standard behavior epics provide. Nothing like SAFe going on.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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