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

How to automatically set the issue due date based on subtask due dates?

Taneli Ylinen

Hi everyone, I am a real newbie to Jira and have been trying to solve this for last 24hours without finding an solution. So under the issues there are few subtasks that have set due dates and I would want Jira Automation to automatically update the issues due date based on the latest subtask due date. So automation would compare sub task due dates and would choose the latest due date and set it to issue duedate.

How can I do this? I have tried tens of combinations but have not succeeded to automatically update the issue duedate (that currently is always empty for all issues as I am only following subtask due dates)

Can someone help me? Like said, I started using Jira 3 days ago so an not familiar with most of the functions it has

Accepted answers

Piotr Zadrożny _Eyzee_

Hi @Taneli Ylinen

The rule that works in my demo is:

When: Field value changed. Fields to monitor for changes: Due date for All issue operations
Condition: Field Issue type equals value Sub-task
Condition If block: Field Due date is after Field Due Date from the Parent issue
Branch rule: Type of related issues Parent
Action: Edit issue, copy Due date from Trigger issue
Else block
Branch rule: Type of related issues Parent
Condition Issue field condition: Field Due date is empty
Action: Edit issue, copy Due date from Trigger issue

If you need any screen from any step please let me know

I used if else statement because without else (checking if Due Date of parent is empty) statement automation rule does not worked when parennt issue does not have Due date field already set.

Best regards,

Piotr

Piotr Zadrożny _Eyzee_

Hi,

Please provide some more info/screenshots that will help us troubleshoot your problem:

Click on TestiDueDate1 rule and then Rule Details - verify who is set as Actor. Is it Automation for Jira or any other user?
In Project Settings click Permission and write down all Users/Groups/Roles selected for permisions: Browser projects, Edit issues, Schedule issues. The user specified as Actor in step 1 should have thjose permissions (if its Automation for Jira there should be added Project role atlassian-addons-project-access)
Make sure you use build-in field Due Date on all screens (both task and subtask) and not some Custom Fields called Due Date
Do you use Issue Security Scheme (you can check it in Project Settings -> Summary -> Permissions -> Issues - if you dont use any you should find there Issues: none)
Do you use Jira Cloud or Server/DC? (I assumed Cloud)
It would be also great if you could make a screenshot on every step in your automation rule 1 to 9
Before every action and branch step you can add another action Log action and in log message provide {{issue.duedate}} which will log in Audit log what was current duedate in an issue. You can then verify Audit log after the test rule execution by clicking the rule and then Audit log

Best regards,

Piotr

All comments

Piotr Zadrożny _Eyzee_

Hi @Taneli Ylinen

The rule that works in my demo is:

When: Field value changed. Fields to monitor for changes: Due date for All issue operations
Condition: Field Issue type equals value Sub-task
Condition If block: Field Due date is after Field Due Date from the Parent issue
Branch rule: Type of related issues Parent
Action: Edit issue, copy Due date from Trigger issue
Else block
Branch rule: Type of related issues Parent
Condition Issue field condition: Field Due date is empty
Action: Edit issue, copy Due date from Trigger issue

If you need any screen from any step please let me know

I used if else statement because without else (checking if Due Date of parent is empty) statement automation rule does not worked when parennt issue does not have Due date field already set.

Best regards,

Piotr

Taneli Ylinen

Thanks Piotr, That setup went through and is now enabled, but however nothing changes on the project? I mean if I modify the sub-task dates, the issue date still remain empty no matter what I do? Am I missing something that would need to be enabled or set to make the automation work? Even the stock automations like "when all subtasks are done -> move parent to done does not take effect when I try.

Taneli Ylinen

Hi, I took a look at the automation logs and from those it seems that the automation should be working, but it will still not change the due date of the issue? It just remain blank always

Erin Quick-Laughlin

Just a few thoughts @Taneli Ylinen

1. Are the Due Date fields the same type of field in parent & child?

2. I'm not sure if it's possible to block the JA user, but if it is, are there special permission or security scheme restrictions on parent issue type?

3. Have you tried adding a logging statement to your JA, to see what value is being picked up from the child?

Piotr Zadrożny _Eyzee_

Hi,

Please provide some more info/screenshots that will help us troubleshoot your problem:

Click on TestiDueDate1 rule and then Rule Details - verify who is set as Actor. Is it Automation for Jira or any other user?
In Project Settings click Permission and write down all Users/Groups/Roles selected for permisions: Browser projects, Edit issues, Schedule issues. The user specified as Actor in step 1 should have thjose permissions (if its Automation for Jira there should be added Project role atlassian-addons-project-access)
Make sure you use build-in field Due Date on all screens (both task and subtask) and not some Custom Fields called Due Date
Do you use Issue Security Scheme (you can check it in Project Settings -> Summary -> Permissions -> Issues - if you dont use any you should find there Issues: none)
Do you use Jira Cloud or Server/DC? (I assumed Cloud)
It would be also great if you could make a screenshot on every step in your automation rule 1 to 9
Before every action and branch step you can add another action Log action and in log message provide {{issue.duedate}} which will log in Audit log what was current duedate in an issue. You can then verify Audit log after the test rule execution by clicking the rule and then Audit log

Best regards,

Piotr

Tijs Tijert

There is no Project role atlassian-addons-project-access in my project.
How do I add it?

Tijs Tijert

Solved

Ahmed Nassar_yybdfb

This worked for me. Screenshot 2023-02-13 153721.png

Ahmed Nassar_yybdfb

Ok, I think this is just much better

Screenshot 2023-02-14 124511.png

Welcome!

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

Quick Links

Find more posts tagged with

atl-gruland

automation