...
Goal | Get a clear view of your team’s backlog | ||||||
|---|---|---|---|---|---|---|---|
Scenario | 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
Let's have a look at how this can be automated using JSU | ||||||
Components |
|
How to configure this rule
Go to Project Settings > Workflows and click Edit for the required workflow.
Choose the transition where you want to perform your post function. In this case, we choose the transition to
.Status colour Green title DONE Select the Post Functions tab and click Add post function.
Select the Update any Issue Field (JSU) post function, then click Add.
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
.Status colour Green title done Select Within same Issue for the issue relation.
Select Epic Status for the Issue Field.
Click Add at the bottom of the page.
Now it's time to create your precondition to prevent errors when the workflow is used for non-epic issues. Click Add post function, select Precondition: Value Field (JSU) then click Add.
Configure your precondition by choosing
Issue type = Epicand make sure the comparison type is String. Click Add.
Publish your workflow.
Now check what you have achieved with JSU. Your epic is currently visible on the backlog. Move your epic to
and go back to your backlog. Your epic doesn't show up anymore!Status colour Green title done
...