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

Automation rule - checking child field date

Paul Smith_pjvnsf

I'm fairly new to automation in Jira and was wondering if someone can say if this is even possible.

I want to be able to set the value of a custom field, RAG status, by comparing the due date of the issue with the due dates of ALL its child issues. Basically:

- if all child issues due date is equal to or before the parent issue due date, set RAG to green

- if one or more child issues due dates are greater than the parent issue due date, but no more than three months, set RAG to amber

- if one or more child issue due dates is 3 months greater than the parent issue due date, set RAG to red

This is on a company managed project, but if possible and a success, we may consider rolling this out as a global automation rule across multiple projects. I do not have any apps to use and it's likely if there was one that could do this, it wouldn't be approved for use in our organisation, so this would have to be achievable out of the box

Accepted answers

All comments

A A Ron Geister _Trundl_

@Paul Smith ,

Good day. This is definitely possible. Let me see if this can help you:

This is something that should help. Here is another link from the community that is doing something similar but can be modified to your use case.
https://community.atlassian.com/t5/Jira-Software-questions/Jira-Automation-Parent-issue-due-date-based-on-children-issues/qaq-p/1592692

Kind regards,

Aaron

Paul Smith_pjvnsf

Thanks @A A Ron Geister _Trundl_ i'll give that a try

Paul Smith_pjvnsf

@A A Ron Geister _Trundl_ How about if the child issues are in different projects and the only thing in the project is the parent issue?

So the example is, we have a Kanban project of parent issues, these issues can have one of more child issues linked within multiple projects and it is the due date of these I want to check.

In the example you have provided, when creating this rule on the parent issues board, the 'for: sub-tasks' will only allow me to use the parent issue as that is all that is in the project. I've tried switching it around and running it on the child issue project with the below but still no luck. Feature is the child issue.

A A Ron Geister _Trundl_

@Paul Smith

Parent is a parent and a child a child. As long as you don't state a project in your automation you should be find.

Now the only caveat is if you make this a project automation vs a global automation. This would need to be a global automation to hit all parents. If you did in the project it would only work for the project related issues I believe.

Hope this helps.

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-software

jira-software-cloud

atl-gruland

automation