Linking Epic Status to the Epic Issue Status

[Ron Becker]

We've updated our Epic workflow to change the Epic status with a post function. So when the Epic workflow status is changed the "Epic Status" is changed accordingly.

The following KB article describes how to do this: https://confluence.atlassian.com/jirakb/linking-epic-status-to-the-epic-issue-status-881516333.html

There is one question left. How to keep Epic status and Epic workflow status in sync when Epic status is changed from the Scrum board (Using "Mark as Done")
We would like to set the issue workflow status to Done when "Mark as Done" is selected from the Scrum board. Is this possible? Or isn't it a good idea at all?

[Stephen Wright _Elabor8_ · Accepted solution]

Hi @Ron Becker

It's not as simple as post-functions and workflow properties only apply to workflow statuses, not the Epic Status.

You'll be able to create this behaviour with an application - such as:

• Scriptrunner
• Automation for Jira - I've seen users suggest this in the past, such as this answer

Personally, I would consider if this is necessary. For our users, we find it more likely they'll transition an Epic to Done via the workflow than via Epic Status.

If we're concerned they'll miss Epic transitions or want them to track more closely we'll:

• Create a project dashboard showing Epic status, used for status reporting
• Create an Epic Kanban board, that they can use at stand-ups / Scrum of Scrums
• Create an issue search which checks for open Epics with no open Stories (note - you need Scriptrunner or a similar JQL enhancing app for this)

Ste

[Ron Becker]

Thanks for your answer. Valuestreams which are concerned that Epic Status and Epic workflow status are not alligned can use a dashboard or filter to check consistency.