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 - Add customfield date into a subtasks based on parent issue

Mateo Colombo

Hi everyone,

I am trying to add a customfield ("Target start", of type date) to a subtask which should be calculated based on the Parent issue "Target start".

So...let's say:

Task A -> "Target start" = 24/04/2023 [ THIS IS THE INFORMATION I HAVE ALREADY ]

Subtask a -> "Target start" = Task A "Target start" - 3 weeks [ THIS IS WHAT I NEED ]

I created an automation as I have multiple Tasks and therefore multiple Subtasks that require this adjustments.

The automation runs smoothly but I am having trouble in parsing the Parent date into the subtask.

Captura de pantalla 2023-02-08 115603.png

I am not sure how should I complete the json part to complete this properly. Can someone suggest me other ways?

Thanks!

Accepted answers

All comments

Trudy P Claspill

Hello @Mateo Colombo

Welcome to the Atlassian community!

Whenever requesting help with an Automation Rule, please show us the entire rule. Edit Issue actions and references to the issue object in smart values rely heavily on the context. Without seeing the entire rule we can't determine the context for this one action to offer you the proper advice.

Is you rule not working as you have written it? How exactly is it not meeting your expectations? What is shown in the rule's Audit Log when the rule executes?

Patricia Francezi_iDev_

Hi @Mateo Colombo

When you need to do actions in different tasks, related, child and parents, you must use the Branch rules.

So you will have options to do all the actions you need.

As far as I understood you are not using branch yet

You can find more information here https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

If you already using branch, as @Trudy P Claspill mentioned, would be great having the screenshot for the whole rule, so we can help you.
https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

Mateo Colombo

Hi @Patricia Francezi_iDev_ !

I am using branches already, I guess.

This is the error I get in the audit log about the parsing of the dates:

Captura de pantalla 2023-02-08 115756.png

Mateo Colombo

Hi @Trudy P Claspill

Thanks for the reply! I already added everything.

Trudy P Claspill

You should not have to use Advanced Editing for this.

Are you able to select the Target Start field directly from the available fields in the Edit action?

Screen Shot 2023-02-08 at 8.35.48 AM.png

Once you pick the field you can enter the smart value you want to use to set it.

Screen Shot 2023-02-08 at 8.37.46 AM.png Screen Shot 2023-02-08 at 8.38.15 AM.png

I do wonder, though, why you are setting the target start date of a subtask to be 3 weeks before the target start date of its parent task.

Bill Sheboy

Hi @Trudy P Claspill

I believe Target Start, and some other advanced roadmap fields, cannot be selected from the Edit Issue dropdown list yet. Instead only JSON edit works for them. Here is the suggestion to fix that: https://jira.atlassian.com/browse/JIRAAUTOSERVER-159

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

cloud

jira-software

jira-software-cloud

automation