Dynamicaly changes the parent ticket field based on the sub-task field

[Lakshmi CH]

Hi Team,

We are looking for the configuration to update the parent ticket field value based on the sub-task field value.

The requirement is :

If the main task has "n" number of sub-tasks, and if the "Scheduled Completion Date" of any subtask is changed to a later date(farthest), we should update the main task with that date. 

Ex : If subtasks "Scheduled Completion Date" are sub-task1 = June 23, sub-task2 =July 20, sub-task3 = July 26, etc., and a user changes any of these sub-tasks to August 12, the main ticket should also changes to August 12th.

[Trudy Claspill · Accepted solution]

Hello @Lakshmi CH 

Have you looked into creating an Automation Rule to handle that?

https://confluence.atlassian.com/automation/

You could create a rule triggered by a change to the sub-task date field.

Then you would branch up to its parent.

Within the branch you would use Lookup Issue to look up all the subtasks.

From the Lookup Issues results you could access the maximum value of the date fields and copy that to the parent issue in an Edit issue action.

[Bill Sheboy]

Hi @Trudy Claspill 

I do not believe Lookup Issues action for Jira Data Center supports custom fields yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

Perhaps using the {{issue.subtasks}} smart value will allow access to the field.  If not, the workaround using Send Web Request and the issue search REST API would be required to set the parent field.

Kind regards,
Bill

[Trudy Claspill]

Good catch, @Bill Sheboy !

[Lakshmi CH]

Hi @Trudy Claspill,

 Do you have any examples of this kind of automation ?

[Trudy Claspill]

@Lakshmi CH 

1. Trigger: Field Changed: specify your date field

2. Condition: confirm the change occurred in a Sub-task

3. For Related Issue: Parent -- changes the focus of the rule to the sub-task's parent issue.

4. Log action: this will print the value that you will next be updating into the parent issue.

5. Edit Issue - this edits the parent issue.

The smart value used in 4 and 5 is {{issue.subtasks.<your date field>.max}}

That smart value will get the maximum value in the specified field from all the subtasks.

[Lakshmi CH]

Thank you @Trudy Claspill . Its working as expected.