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

Copy the fields values into another field

Lusine

Hi everyone,

I have the following problem:

I am dealing with an issue type that involves subtasks, and I need to copy the value of a specific field from each subtask and consolidate them into one field in the main task.

The fields represent users from our company and offer multiple choices.

For example:

Subtask 1 - Field value: user1, user2, user3

Subtask 2 - Field value: user4, user5

Subtask 3 - Field value: user6, user7, user8, user9

Main task - Field value: user1, user2, user3, user4, user5, user6, user7, user8, user9

Accepted answers

Kalyan Sattaluri_iinm1n

Hello @Lusine

What kind of field is this? Multi Checkbox field?
What is the trigger for your rule?
- Field change on sub-task?
- Scheduled Trigger to do this sync every day irrespective of if Sub-tasks had any changes?
You tagged it as DC, do you have lookupIssues action available in Automation?

All comments

Kalyan Sattaluri_iinm1n

Hello @Lusine

What kind of field is this? Multi Checkbox field?
What is the trigger for your rule?
- Field change on sub-task?
- Scheduled Trigger to do this sync every day irrespective of if Sub-tasks had any changes?
You tagged it as DC, do you have lookupIssues action available in Automation?

Lusine

Hi @Kalyan Sattaluri ,

Thanks for responding.

It's a field where I can select multiple users.
I need this automation to trigger when the statuses of the subtasks are changed to "done".
The field will remain unchanged after the automation.
This action will be performed only once for each main task.

I require several employees to provide the names of the users from their respective directorates.

It will help a lot if you could help.

Kalyan Sattaluri_iinm1n

Thanks for your response. Few more questions.

I understand your overall ask, that is, Main Task should have all values from sub-task, but, If a sub-task is transitioned to Done, do you want just that sub-task's value sync'd over to the parent, or, every time a sub-task is transitioned, we sync values from *all* sub-tasks even if they are not done? There is a difference between the 2 I mentioned above. Nothing complicated, but just want to clarify.
Please share what is this field called exactly in the sub-task issue. Share a screenshot of the field because we need to know the exact field value for this to work.
Please confirm that the story issue also has the same field, field name, field values.
Please clarify if you have lookupIssues action available?

Just FYI for future steps- we may need to know the customfield value of this field if referencing the field name does not work. But we will get there that comes.

Lusine

No problem, Thanks for your help.

I don't need the transition to occur each time one of the subtasks is completed. It should only activate when all the subtasks are done.
The attached screenshot displays the field in question.
Yes, the main task also possesses the same field where I intend to transfer the values from the subtasks.
Please tell me how can I look if I have that action or not

Screenshot 2024-04-05 172412.jpg

Bill Sheboy

Hi @Lusine

First thing, I am using Jira Cloud, not Jira Data Center, and so cannot test the suggestions I offer. They are based on what I know about automation rules, in general. With that out of the way...

I believe there may be two ways to solve this. Let's check the easiest one first:

Issues have the subtasks smart value: {{issue.subtasks}} However, that may not include all of the data for each subtask, such as your user field. The way to check that is using this how-to article, looking at an example issue with subtasks which have the user field set, and observe what you see.

https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html

If you see the data for the users, the rule could use an iterator and advanced edit with JSON to add the users to the parent issue.

If the users were not visible for the subtasks, you can use the REST API to perform an issue search to load the subtask, and then use the same iterator and advanced edit technique on the results.

FYI, with Data Center, rules also have the Lookup Issues action, but I do not believe that has custom fields yet and so it will not help this scenario.

Kind regards,
Bill

Lusine

Hi @Bill Sheboy ,

Thank you for your reply. I'm trying the way suggested below. But thanks a lot for your support.

Best regards,

Lusine

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

data-center

jira-software-data-center