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

Creating a subtask 30 days after completing the previous one

Мария_q2epve

Good afternoon.

My condition is to create a subtask "delete the server" 30 days after completing the previous subtask "turn off the server" (this subtask is created using automation), these subtasks have one parent. I'm trying to do this through jira automation, but it doesn't work for me.

In jql, I specify the following expression: project=“AS” and summary ~ “Turn off the server” and issutype= “Subtask_as” and resolved <= 30d

By this expression, subtasks completed more than 30 days ago are found. But it does not create a new subtask.

Please help me solve this problem. Maybe there's another way.

Accepted answers

Trudy P Claspill

Hello @Мария

Please show us the complete automation rule you have constructed. We can't advice you on why it is not working without that information.

Also please show us the output in the rule Audit Log for an execution of the rule where you did not get the results you expected.

All comments

Trudy P Claspill

Hello @Мария

Please show us the complete automation rule you have constructed. We can't advice you on why it is not working without that information.

Also please show us the output in the rule Audit Log for an execution of the rule where you did not get the results you expected.

Мария_q2epve

Automation is triggered if I make changes to any field. If the task just went through the business process and got into "completed", then audit log reports - no actions performed.

Trudy P Claspill

Based on your screen images it appears that you are using Jira Server or Jira Data Center. Is that correct?

The message, along with the settings in your rule Trigger, explain your issue.

Your rule Trigger has the box checked to include only the issues that have changed since the last time the rule ran. The message says no issues have change since the last time the rule ran. So your rule is not executing any actions.

Do you have subtasks that match the JQL in your trigger where those subtasks have been changed since the last time the rule ran?

Мария_q2epve

Good afternoon. I need this checkmark because I don't need automation to create subtasks in parent tasks where they have already been created before. Every day we create and execute subtasks "Turn off the server". The transition of a task in a business process from a new one to completed, is it considered an update of the task??? Example: the last execution of the rule was on 06/24/2023, today there is a task with a solution from 05/29/2023 (30 days from the date of the solution), the rule should work today on 06/29/2023, but it does not work on this task, apparently it does not see any changes on it… although the jql filter defines this task.

Мария_q2epve

@Trudy P Claspill

Thank you very much for your help, the search for your proposed jql works correctly! That's what I needed.