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 from a Value Change in JSP to Edit related field in it's linked issue in JDP

Selena Peri

Kia Ora,

Working on setting up Automation rule between two projects (one is JDP and the other is JSP).
I have successfully setup a automation rule from a value change in JDP to then edit linked issues (e.g., relates to) corresponding field.

However, when I try to setup a automation rule going the other way (value change in JSP to then edit linked issues (e.g., relate to) in JDP the rule fails,

I have create the automation rule as follows (from value change in JSP to edit related field in it's linked issues (e.g., in JDP):
Screenshot 2024-06-29 090233.png
I have also typed in the box below Business Value Outcome: {{triggerIssue.customfield_10504}}

I have research round and round but can't get the field working... my audit lot is:
Screenshot 2024-06-29 090040-.png

When I go to Jira Setting -> Custom Fields... I'm unable to see "any of the JDP" fields in this view.

TIA for any support.

Accepted answers

All comments

Bill Sheboy

Hi @Selena Peri

First thing, I note Edit Issue action appears to have the "Business Value Outcome" field selected from the dropdown list and updated using JSON (using its custom field id). Only one of those methods may be used for a specific field at a time in a single edit. Please try removing the JSON and pasting the smart value expression into the field edit:

Next, what type of field is customfield_10504: text, single-select option, multiple-select option, etc.? The type of field may impact how to perform the edit of the JPD field.

Same thing for the JPD custom field, "Business Value Outcome".

Finally, issue linking is often directional, especially for JPD <-> JSP (Jira Software Project). But your branch is checking link types which are in both JPD and JSP issues.

If you want the branch to select the JPD idea for the JSP trigger issue, please change the branch to only check "implements".

Kind regards,
Bill

Selena Peri

Kia ora Bill,

Thanks for your reply!

You are correct I had been testing using JSON code (as I was trying all various ways...)... when trying on way I didn't have JSON code in there and it was only {{triggerIssue.customefield_10504).

Customfield_10504, a JSP field, is setup as field type: radio button. The linked issue field, in JDP (the field to be edited), is field type: multi-select (customfield_10565).

Still no luck as per screenshots (updated rule and audit log outcome after retrying): Screenshot 2024-06-29 102830.png
Screenshot 2024-06-29 102325.png

Selena Peri

One thing that is interesting is that in Jira Setting > Custom Fields, I'm unable to see any JDP custom fields. Is this normal? Through research it seems one should be able to see all "custom fields" in Jira Settings...

I have admin rights in both projects that I'm working with too.

Bill Sheboy

Thank you for that information!

As the JSP field customfield_10138 is a radio button, it will return the text of the selected option with either of these:

{{issue.customfield_10138}} or {{issue.customfield_10138.value}}

Does your JPD custom field customfield_10565 have exactly the same options as the JSP one? If not, setting the field cannot work.

If they match, you may set the value as I described earlier:

select the JPD field in the dropdown list
enter the smart value expression {{issue.customfield_10138}}
when the value appears below the field, select it for use in the edit

I just tested this and it does work for a JPD, multiple-select custom field.

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-cloud

jdp