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; } } }

Automatically change epic status when 2 specific subtasks done

Umar Maroof

I am trying to do a automation where under epic I have 2 subtasks

name frontend publish and backend publish

I want when both subtasks status turns done then epic status automatically change to ready for testing below is the rule which I try but its not working

sub change.png

Accepted answers

Hana Kučerová

Hi @Umar Maroof ,

your automation rule looks good. Have you tried to look into audit log, where is the problem? Would you please share the screenshot from there?

Bill Sheboy

Hi @Umar Maroof

Subtasks are not normally used with a parent Epic, but instead their parents are stories, tasks, or bugs.

If you actually are associating subtasks with an epic directly, I suspect the branch for epic (parent) will not work in the rule. Instead you could try either...

using what was intended in Jira and having story/task/bug as children of the epic, or
change your branch to use JQL to find the parent with key = {{triggerIssue.parent.key}} AND issueType = Epic

Kind regards,
Bill

All comments

Hana Kučerová

Hi @Umar Maroof ,

your automation rule looks good. Have you tried to look into audit log, where is the problem? Would you please share the screenshot from there?

Bill Sheboy

Hi @Umar Maroof

Subtasks are not normally used with a parent Epic, but instead their parents are stories, tasks, or bugs.

If you actually are associating subtasks with an epic directly, I suspect the branch for epic (parent) will not work in the rule. Instead you could try either...

using what was intended in Jira and having story/task/bug as children of the epic, or
change your branch to use JQL to find the parent with key = {{triggerIssue.parent.key}} AND issueType = Epic

Kind regards,
Bill

Umar Maroof

@Hana Kučerová Audit log No action performed

Hana Kučerová

Thank you, @Umar Maroof . Would you please share the whole record (not only the result)? This way it won't help much.

@Bill Sheboy is correct, I didn't realize you are probably trying to connect Epics and Sub-tasks and conditions with Sub-tasks should be replaced.

Umar Maroof

@Hana Kučerová

Thank you for your respones Actually now I change the logic now I create one sperate task under epic and create two subtasks under that tasks and create sperate rule to change the epic status depend upon that task status and task status depend upon subtasks status and now its working fine for me.

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