Is there a way to modify the Child issue's date field from the parent issue

[Bhushan Naga _ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED _]

I have a Target end field in a child issue and I want to modify it from the parent issue, is there any way to achieve this 
Appreciate your help

[Jaime Escribano · Accepted solution]

Hi @Bhushan Naga _ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED _  and wellcome to the community!

Yes, there is a quick way of doing this. When an issue has sub-tasks assigned to it an excel-like view will appear. You can add your desired fields and edit them directly from the parent issue. 

See the following images for an example:

Hope that was helpfull!

Regards,

Jaime Escribano

[Bhushan Naga _ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED _]

Hi @Jaime Escribano 

Thanks for the response, I am unable to edit the Target end field after double clicking 

[Jaime Escribano]

It is possible that your user doesn't have the "plan work items" permissions?

Without it you cannot modify the delivery dates in general :O 

Regards,

Jaime

[Weronika Hałdaś_Deviniti_]

Hi @Bhushan Naga _ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED _ ,

You can achieve it with automation rules. I'm not sure if you need to update the already existing child issues or newly created ones; therefore, I'm sharing two examples: 

Rule 1. Update field value on child issues when the parent is updated

Steps to Create the Rule

1. Create a new automation rule

   1. Set the trigger to Field Value Changed

   2. Set Fields to monitor for changes to “Initiative Priority”

   3. Set Change type to “Any changes to the field value”

2. Add an If condition and select {{smart values}} condition

   • Set First value to {{issue.customfield_10068.value}}

   • Set Condition to does not equal

   • Set Second value to Empty

3. Add a Create variable Action

   1. Set the Variable name to “customval”

   2. Set the Smart value to {{issue.customfield_10068.value}}

4. Add a Branch rule / related issues branch

   1. Set Type of related issues to “JQL”

   2. Set the JQL field to “parent = {{issue.key}}”

   3. Uncheck the box Only include issues that have changed since the last time this rule executed

5. Under the branch, create an Edit issue Action

   1. For the custom field in question "Initiative Priority", set the value to be the variable of {{customval}}

Save and publish the rule.

Rule 2. Update field value on newly created child issues

Steps to Create the Rule

1. Create a new automation rule

   1. Set the trigger to Issue Created

2. Add an If condition and select Related issues condition

   1. Set Related issues to Parent

   2. Set Condition to Exists

3. Add another If condition and select {{smart values}} condition

   1. Set First value to {{issue.parent.customfield_10068}}

   2. Set Condition to does not equal

   3. Set Second value to Empty

4. Add a Create variable Action

   1. Set the Variable name to “customval”

   2. Set the Smart value to {{issue.parent.customfield_10068}}

5. Add an Edit issue Action

   1. Set the value of the custom field to be {{customval}}

6. Add a Branch rule / related issues branch

   1. Set Type of related issues to “JQL”

   2. Set the JQL field to “parent = {{issue.parent.key}}”

   3. Uncheck the box Only include issues that have changed since the last time this rule executed

7. Under the branch, add an Edit issue Action

   1. Set the value of the custom field to be {{customval}}

Save and publish the rule.

The cases are described here. 

There are also plugins such as Issue Templates for Jira, which, in addition to the ability to create entire structures based on a template automatically, also offer the Smart Defaults  feature that allows setting date fields in child issues based on dates in the parent issue during structure creation. 

I hope the above tips will be helpful :) 

Kind Regards,
Weronika

[Bill Sheboy]

Hi @Weronika Hałdaś_Deviniti_ 

As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information about this, please see:

Atlassian Partners - Rules of Engagement

https://community.atlassian.com/t5/App-Central-articles/Atlassian-Partners-Rules-of-Engagement/ba-p/2899328

Kind regards,
Bill

[Weronika Hałdaś_Deviniti_]

Hi @Bill Sheboy 

You're right! Thank you very much for the reminder!

I've only recently started being active on the Community, so I appreciate your message even more - it will definitely help me avoid similar oversights in the future :) 

Kind Regards,
Weronika