Sub Issue custom filed value need to be display in the Parent filed

[Ravi Kumar]

Hi Team,

we have a requirement like , 
All the sub issues custom filed like Name of the user needed to be displayed in the Epic Custom filed Name of the User , do we have any automation rule to achieve it ?

Regards,

Ravi

[Trudy Claspill]

Hello @Ravi Kumar 

When do you want to copy the values? Only when the sub issue is created, or whenever the fields in the sub issue change? What if there are multiple sub issues and they don't have the same values in these fields - how should the parent issue field be set then?

There is not a template in the Automation library for this.

Have you tried to create the rule? Show us what you have so far. What part are you struggling with?

[Ravi Kumar]

Hi @Trudy Claspill ,

Thanks for the quick response .

Let me explain the situation , we have Epic and we add the the stories through an issues links , so whenever any issue(Story or any issue type)  added to that epic we need that story custom filed value (Single filed ) to be copied and displayed in the epic custom filed . We have same Custom filed in both Epic and Story , so the Sub issue (Story ) custom filed values to be copied and updated in the Epic .

Here the Data should need to be copied in two cases , 1. when the Sub issue added in any case like issue links and 2. when an sub issue (Story) custom filed is updated.

I have tried a automation rule but not sure what are the properties need to be take , So can you please explain to me what are the exact conditions and actions needed to be in the automation rule.

Please let me know if you need more details on the same.

Regards,

Ravi

[Trudy Claspill]

Hello Ravi,

For information about the components of an Automation Rule refer to https://support.atlassian.com/cloud-automation/docs/components-in-jira-automation/

I would like to help you learn how to reason out creating the rules rather than just do the work for you. If you have not done much work with Automation Rules before, this is a bit complicated for your first try.

The first thing you need to figure out is what activity you want to trigger the rule. Generally you can have only one type of event trigger a rule. You've mentioned two types of events - issue linking, and updates to fields. So, you are going to need two rules. There are a couple of things you need to clarify about these triggers:

1. When you say that an issue can be "linked" to the Epic do you mean that it is made a child issue of the Epic or are you talking about the generic issue linking functionality where you could set the relationship to things like "blocks" or "depends on" or "duplicates"?

2. What about when one of these sub issues is first created? Could the field be set then, and could the sub issue also be linked to the Epic during creation? Issue Created is a different event than Field Updated.

3. If the Epic has just one of these custom fields, but can have multiple sub issues linked to it and each sub issue might have a different value in the custom field, then how do you decide if the Epic should be updated? Do you just keep overwriting the value in the Epic with whichever sub issue was updated or linked last?

Maybe you want to focus on just one scenario at a time, work through the rule for that, then work on the next scenario.

Can you review the documentation, and start working on creating a couple of rules, and show us what you figure out for the Trigger for each of these rules?

Deciding which component to use after you define the trigger component will depend in part on your answer to #1. In either case you will need to add a Branch component to find the related issue - the Epic. The options you choose for the Branch component depend on how you are creating the relationship between the sub issue and the Epic. If you are using the built-in Epic/Child Issue functionality then you would choose the Related Issue and Type of Related Issue would be "Epic (parent)". If you are using generic issue linking functionality then the Related Issue type would be "Linked Issues".

Once you have your Branch defined to find the correct Epic, then you would need an Edit Issue action where you would select the field you want to update in the Epic and specify how to set it. If the same field exists in the sub issue, then you could use the "Copy from Trigger Issue" to copy the value from the sub issue that triggered the rule.

You may want or need to include Conditions before the Branch and/or within the Branch if there are other things you want to check before taking any action. Examples might be that you only want to copy the value if the sub issue is a particular type of issue, like a Story, or only if the field in the Epic is blank.