nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation: Trigger when child removed from Epic

Karin.Gleichauf

I built an automation to set epics "done" when all children are "done". When a new task becomes child by adding the epic link the epic is again set to "in progress".

When the epic link is removed on the task (so there is no more child in the epic not "done") the epic should be moved to "done" again, but I can't find the proper trigger for this rule. (Don't like to use a scheduled rule to check whether all children are done in an epic).

Has someone an idea how to solve this?

Best regards

Karin

Accepted answers

Mark Segall

Hi @Karin_Gleichauf

Since we're not able to perform JQL against historical Epic Links, it will not be possible to key off of a previous Epic association. For example, you would need a function that simply doesn't exist:

TRIGGER: Field Value Changed (Epic Link)
BRANCH Previous Parent

So, you have to go at this from the epic itself and that means a scheduled rule is unfortunately really the only way to go because there is similarly no ability to trigger when child issue added/removed

I hope this helps explain why the scheduled trigger is really the only option.

Trudy P Claspill

It is possible to create a rule that is triggered on Issue Updated and then check the change log to see if it was the Epic Link field that changed, and pull the before and after values of the field. From there you would be able to get back to the Epic and evaluate the status of the child issues.

Note though that the rule would be triggered on every issue update. You can zero in on the Epic Link in the trigger itself.

The response from @Bill Sheboy on this post discusses this.

All comments

Mark Segall

Hi @Karin_Gleichauf

Since we're not able to perform JQL against historical Epic Links, it will not be possible to key off of a previous Epic association. For example, you would need a function that simply doesn't exist:

TRIGGER: Field Value Changed (Epic Link)
BRANCH Previous Parent

I hope this helps explain why the scheduled trigger is really the only option.

Karin.Gleichauf

Hi Mark,

thank you very much. I hoped for a trigger like "issue link deleted" but expected there is none for the epic-child-relationship. So I will have to go for the scheduled rule.

Trudy P Claspill

Note though that the rule would be triggered on every issue update. You can zero in on the Epic Link in the trigger itself.

The response from @Bill Sheboy on this post discusses this.

Karin.Gleichauf

Hi Trudy,

thanks a lot! When I have received the issue-key of the Epic by {{#changelog.epic link}}{{fromString}}{{/}}, how can I branch my rule to evaluate the status of the child issues of that epic and not of the trigger issue?

Best regards

Karin

Mark Segall

You can use a JQL branch:

Key = {{#changelog.epic link}}{{fromString}}{{/}}

Trudy P Claspill

@Karin_Gleichauf

@Mark Segall and I were talking this over, and came up with this solution.

TRIGGER: issue Updated

CONDITION (Advanced):

  - {{#changelog.epic link}}{{fromString}}{{/}}

  - Does not equal

  - {{#changelog.epic link}}{{toString}}{{/}}

BRANCH (Advanced): varEpicLink

  - {{#changelog.epic link}}{{fromString}}{{/}}

  - CONDITION

    - status != Done

  - ACTION: Lookup Issues

    - "Epic Link" = {{varEpicLink}} AND status != Done

  - CONDITION (Advanced)

    - {{lookupIssues.size}}

    - Less Than

    - 0

  - ACTION: Transition Issue to Done

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud