Epics use the custom "Epic Status" field to decide whether they show in the board or not. Parallel to this they can have any per-project-workflow. The 2 states can contradict each other and tend to confuse users.
* Are there any recommendations on how to ease the workflow and reduce the confusion due to the parallel workflow & Epic status? I found this so far: https://confluence.atlassian.com/display/AGILEKB/HowTo%3A+Track+Epics+in+the+Control+Chart
* Is there a reason why Jira Agile does not provide a default Epic workflow that can be used instead of the "Epic Status" field?
Hi @Fabian Ehrentraud, can't recall if I sent this direct or not.
We use a post-function to update the value of the Epic Status field on transition. That is then used to help us calculate the cycle time of the Epics. Works on Jira Cloud too.
This is detailed in Understanding the cycle time of epics in Jira. (no email required)
Hope that helps.
I've discovered the same and it totally sucks - especially if you use backlog and use "mark as done" functionality which actually changes epic status instead of Issue Status....
We decided to create a filter to help users to filter the epics in the panel by looking at the number of completed tasks instead of using epic status field.
Additionally we show Epic Workflow Status label. That way its easy to find done epics (Status field Done) having "Epic Status" field open
It has been released soon as part of the Agile Board Filter
The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’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