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

Jira Automation: Send E-Mail when all sub-tasks are done

Sebastian Vanauer_ec7ccx

Dear Community,

I have a problem with my automation.

I have build an automation that checks if all sub-tasks of an issue are done (ACCEPTED in our naming).

Screenshot 2024-06-20 091521.png

If so then the automation should send an email to user XXX.

The automation is working actually BUT it's sending a email everytime when a sub-task has marked as done. The working condition was configured as "ALL MATCH SPECIFIED JQL". So I expect, that the automation only sends an email when ALL sub-tasks matches the condition.

I hope you have an idea about a solution

Thank you very much!

Sebastian

Accepted answers

Ste Wright

Hi @Sebastian Vanauer

I gave this a go, and it works as expected for me.

The email has the exact wording on this rule? There isn't another rule or notification scheme which could be sending the email?

Also, what does the audit log say for entries where the sub-tasks are not all Accepted?

Ste

All comments

Ste Wright

Hi @Sebastian Vanauer

I gave this a go, and it works as expected for me.

The email has the exact wording on this rule? There isn't another rule or notification scheme which could be sending the email?

Also, what does the audit log say for entries where the sub-tasks are not all Accepted?

Ste

Sebastian Vanauer_ec7ccx

Hi Ste,

yes I have no idea what have changed now it's working as expected again.

I hope this will stay now.

Thank you very much for checking this with me

Best Regards
Sebastian

Juan Carlos Pin

Hi @Sebastian Vanauer @Ste Wright

Same here, working for me with the same example. Maybe the transition "Supplier is Available or Newly..." has an automation to notify whenever a subtask gets there.

Regards!

Bill Sheboy

Hello, all!

I rarely use the Related Issues Conditions because in my experience with automation rules:

they occasionally do not work as expected, showing no errors in the log, and
there is no documentation of how they are implemented to work.

My hypothesis is there are timing problems between the gathering of issues and the testing of the condition selected.

My workaround when they stubbornly (or intermittently) do not work is to use the Lookup Issues action with JQL and a Smart Value Condition to exactly test what is needed.

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud