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

Send notification to assignee if no sub-task is created (via Automation)

Lukas_jh1ro7

I have an issue and this issue has no due date, but some approval date. What I want to achieve via automation is to send notification to assignee, if there's no sub-task with due date after some time, for example one month, after approval of the parent issue. So that means, one month after issue approval, it should be there at least one sub-task with due date, if no due date notify the assignee of parent issue or if no sub-task the same notification should go to the parent issue assignee. How can I implement this workflow via Automation?

Accepted answers

Bill Sheboy

Hi @Lukas

How are you determining "issue approval": status transition, a custom field, something else?

However you are doing that, you could write an automation rule with a scheduled trigger to check your various conditions and then send the notification. I recommend mapping out this process better before you start; that will help you create the rule, knowing which conditions to test and on which issues to do so.

To get you started on creating your rule, please review this documentation and examples:

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Lukas

How are you determining "issue approval": status transition, a custom field, something else?

To get you started on creating your rule, please review this documentation and examples:

Kind regards,
Bill

Lukas_jh1ro7

@Bill Sheboy yes, the approval date should be filled before the status is transisioned, it's a condition. What I can't imagine is, how can I express the condition "at least one sub-task should be there after one month" in JQL

Bill Sheboy

The smart value for an issue's subtasks is {{issue.subtasks}} and that is a list attribute.

And the size function can be used on that list to check how many subtasks are present. I recommend adding a default value of zero to handle when there are none in your condition test.

{{issue.subtasks.size|0}}

Lukas_jh1ro7

@Bill Sheboy ok, that make sense, however I have couple of "custom" types of sub-tasks. So it should be there at least one sub-task from type of "Mitigation task". How can I take this condition into account?

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