Automatically remove a closed Epic from the Backlog


Requires JSU 2.0+

 Clean up your team's Backlog screen

Do your epics stay in the backlog of your Jira agile board after closing them?

Here's why. Besides the workflow status, epics have an additional field called Epic status which is only accessible on the Backlog screen. Only epics with the Epic status field marked as "Done" are removed from the backlog. Let's have a look at how this can be automated using JSU's Update Any Issue Field post function.

How to configure this workflow

  1. Go to Project Settings > Workflows and click Edit for the required workflow.

  2. You can choose the transition where you want to perform your post function. In this case, we choose the "Done" transition.

  3. Select the Post Functions tab and click Add post function.

  4. Select the Update any Issue Field (JSU) post function, then click Add.

  5. Because we want this post function to perform only for Epics, we will need to configure a precondition. Therefore, we set the precondition to be true at the beginning of the post function configuration. In this transition, you want to have your Epic status updated to "Done". Fill out the fields and click Add.

  6. Now it's time to create your precondition to prevent errors when the workflow is used to non-Epic issues. Click Add post function, select Precondition: Value Field (JSU) then click Add.

  7. Configure your precondition by choosing Issue type to be equal to Epic and make sure the comparison type is "String". Click Add.

  8. Publish your workflow.

  9. Now check what you have achieved with JSU. Your Epic is currently visible on the Backlog. Move your Epic to "Done" and go back to your Backlog. Your Epic doesn't show up anymore!

How-to video

Watch this video to see all of this in action*:

This was only a bit of JSU in action. Subscribe to our YouTube channel and Access more JSU use cases.
See also the app documentation for some more examples and configuration screenshots.

*The video was created on the Jira Server environment. 

Need more information or help? Get in touch!