{"id":750,"date":"2020-03-31T22:31:59","date_gmt":"2020-03-31T20:31:59","guid":{"rendered":"https:\/\/www.actonic.de\/?p=750"},"modified":"2025-07-22T17:14:29","modified_gmt":"2025-07-22T15:14:29","slug":"epic-status-and-workflow-status","status":"publish","type":"post","link":"https:\/\/actonic.de\/en\/epic-status-and-workflow-status\/","title":{"rendered":"Epic Status and Workflow Status"},"content":{"rendered":"

[vc_row][vc_column][vc_column_text css=””]<\/p>\n

Do you work on agile projects and organise your user stories not only with Components and Versions, but also with Epics? When you use Epics, you can sometimes face the following issue: the Epic is closed, however, it still appears on the Epic panel, because an Epic has two statuses – a Workflow status and an Epic status, which are independent. A bit annoying, isn’t it? So, what can you do in order to bring different statuses together? We can suggest a solution.<\/p>\n\n\n

\"\"<\/a><\/figure>\n\n\n

The Problem<\/h2>\n\n

First of all, let’s have a closer look at the problem and try to break it down to smaller chunks:<\/p>\n\n\n

    \n
  1. You should distinguish between Status and Epic Status, as they are completely independent of one another;<\/li>\n
  2. If the Epic Status is closed (in the Backlog) it doesn’t necessarily mean that the Status is closed, too;<\/li>\n<\/ol>\n\n\n
    \"\"<\/a><\/figure>\n\n

    3. Vice versa, if the Workflow Status is closed it doesn’t automatically result in the Epic Status switching to “closed” as well. Moreover, you can’t apply any changes to the Epic, if issue editing in the closed status is disabled, which is a problem. So, you have to reopen the corresponding Epic, set the Epic Status to closed and change the Epic workflow status in the issue view to closed.<\/p>\n\n\n

    \"\"<\/a><\/figure>\n\n

    As you can see, the process is very inconvenient, especially if you have to do it on a regular basis. Obviously, you need to define a workflow which will help you tackle the issue quickly and automatically. We have done our research and here’s what we suggest.<\/p>\n\n\n

    The solution<\/h2>\n\n

    If you are facing the problem described above, try taking the following steps.<\/p>\n\n

    Please note: in this example, we are using the Software Simplified Workflow, the name of your transitions may be different.<\/em><\/p>\n\n\n

      \n
    1. Select All transitions<\/strong> of the closed Status<\/li>\n
    2. Click Post Functions, <\/strong>then Add post function<\/strong><\/li>\n
    3. Select Update Issue Custom Field<\/strong> and press Add<\/strong><\/li>\n
    4. Select the Epic Status<\/strong> from the Issue Custom Field <\/strong>dropdown<\/li>\n
    5. Add the Custom Field Value. <\/strong>In our example, this Value should be Done<\/em>.
      (If you are adding the transition for To Do, fill in To Do, for Done – fill in Done, etc.)<\/em><\/li>\n
    6. Click Add<\/strong><\/li>\n<\/ol>\n\n

      Now, the Epic Status will reflect the Issue Workflow Status once the status of the Issue is closed. We hope this helps.<\/p>\n\n

      References: https:\/\/confluence.atlassian.com\/jirakb\/linking-epic-status-to-the-epic-issue-status-881516333.html<\/a><\/p>\n\n\n

       <\/div>\n\n\n
      \n\n\n
       <\/div>\n\n

      Check out our other articles:<\/p>\n\n\n