Hello, I have a question that is probably simple, but I can not figure it out and would appreciate the help of the Atlassian community. It is on a JSM project. When a work item is created: * browse if there are existing work item from same reporter (OK) * go through all existing work item from this reporter (foreach branch) and check if a specific custom field is not empty (OK) * copy the value of this custom field (from the work item of the foreach) to the work item that triggered the rule The last part is where I struggle. * I have tested with "Edit work item", but it edits the work item of the foreach branch. * I have tested with "Set issue property" (but it the property is associated to the work item browsed in the foreach branch, not to the work item that triggered the automation). It seems to me that it should be rather simple, and that I am missing something... With many thanks! Céline

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

Automation: Copy custom field value from SQL item search (foreach branch) to current work item

Céline - Maestrel

Hello,

I have a question that is probably simple, but I can not figure it out and would appreciate the help of the Atlassian community.

It is on a JSM project.

When a work item is created:

browse if there are existing work item from same reporter (OK)
go through all existing work item from this reporter (foreach branch) and check if a specific custom field is not empty (OK)
copy the value of this custom field (from the work item of the foreach) to the work item that triggered the rule

The last part is where I struggle.

I have tested with "Edit work item", but it edits the work item of the foreach branch.
I have tested with "Set issue property" (but it the property is associated to the work item browsed in the foreach branch, not to the work item that triggered the automation).

It seems to me that it should be rather simple, and that I am missing something...

With many thanks!

Céline

Accepted answers

Bill Sheboy

Hi @Céline - Maestrel

Once the rule is inside of the branch to work items, the scope is now those work items: it cannot edit the trigger one.

Perhaps use the Lookup Work Items action with a JQL expression to find the ones you need, and then reference the {{lookupIssues}} smart value (outside of branching) to update the trigger work item.

Kind regards,
Bill

All comments

Anandhi Arumugam _Cprime_

Hi @Céline - Maestrel I believe you are building this solution using Automation rule. I have a question generally where

copy the value of this custom field (from the work item of the foreach) to the work item that triggered the rule

Say, a reporter Mr.X has created IT-12 (with Field A: "ASD"), IT-14 (with Field A: "<Empty>"), IT-15 (with Field A: "<Empty>") in the past. Now he has created IT-16 (with Field A: "AWD"), which will trigger the Automation Rule.

Now, the system will go through the issues and identify the issues IT-12, 13 and 14. Now the system will copy the value from IT-16 to IT-14 and IT-15. But is it just one value that should be used for the field? What are the other values? How do you check the relevance to the issues where it is empty?

Céline - Maestrel

@Anandhi Arumugam _Cprime_ Thank you!

I wish to update the field of newly created work item only if it is empty. Got this covered OK
In my SQL search, I order the result. I will to copy the latest one set (if there have been various work items with this field set).

I have as well tested to use Variables (as it seems more appropriate than Issue property), but I still can not make it work...

Rule - Using Issue property

Rule - Using Variables

Results of both rules

For both rules, I have the correct values logged in the branch. I know that I have retrieved what I need. However, I can not figure out how to use these values to update the work item that triggered the rule (the one not in the branch), to be updated with these values.

Céline - Maestrel

In other terms, here is a summary of my different questions:

how do I set a value for a field of the work item that triggered the automation, when I am in a foreach branch that loop on other work items?
how do I use a variable (created in the foreach branch) to set the value of a work item field as the value of the variable? I wish to use the variables outside the branch.
Additional question : in my context, would it be best to use "Lookup items" rather than a SQL condition with a foreach?

Thank you!

Bill Sheboy

Hi @Céline - Maestrel

Once the rule is inside of the branch to work items, the scope is now those work items: it cannot edit the trigger one.

Perhaps use the Lookup Work Items action with a JQL expression to find the ones you need, and then reference the {{lookupIssues}} smart value (outside of branching) to update the trigger work item.

Kind regards,
Bill

Céline - Maestrel

Thank you, this is very helpful! I will try this then.

Céline - Maestrel

Hi @Bill Sheboy, thank you for your help. "Lookup work items" was what I had to use. Much more straightforward and easy to use.

I copy below my rule, for whoever comes across a similar need/question.

Lookup item rule.png

Bill Sheboy

Well done, @Céline - Maestrel !

One more suggestion for your rule...

The Work Item Created trigger has known racetrack / timing problems, and so the rule can start before all of the field data is ready to be used. This can cause weird errors and unexpected behavior, such as conditions not matching. The symptom does not always happen, although it can mysteriously start after a rule has been working with no problems for a long time.

In a recent post from an Atlassian team member working on automation, they noted they are working on architectural changes to fix this defect.

For now, the mitigation for this defect is to always add the Re-fetch Work Item Data action immediately after the trigger. This will slow the rule slightly and reload the data before the steps proceed.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management