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

Empty value returns with a successful "edit additional field" automation

Kemal Solmaz

Following json is successfully perfomed with the automation rule that is running to update the value for the "Found in version" from the jira field "Affects versions". However "found in version" field still returns as empty value on the test issue. Can you please advise.

{ "fields": { "customfield_13981": { "value": { "id": "{{issue.customfield_11644}}" } } } }

Screenshot 2024-12-04 at 13.56.28.png Screenshot 2024-12-04 at 13.57.29.png Screenshot 2024-12-04 at 14.01.34.png

Accepted answers

Kai Becker

Hi @Kemal Solmaz

welcome to the community and thank you for your question.

What type has the Found in version field?
Why not just simply copy the value from one field to the other using edit issue?

Florian Bonniec

Hi @Kemal Solmaz

If Found in version is a single select version picker. You need to push only 1 value to the field. But Affects Version is a multi version picker. You could use smart value on the edit field directly and not use the Advanced edit with json.

Smart value could be {{issue.versions.last}}

Regards

All comments

Kai Becker

Hi @Kemal Solmaz

welcome to the community and thank you for your question.

What type has the Found in version field?
Why not just simply copy the value from one field to the other using edit issue?

Florian Bonniec

Hi @Kemal Solmaz

Smart value could be {{issue.versions.last}}

Regards

Kemal Solmaz

Thank you @Kai Becker

it's Version Picker (single version) type.
I tried first copy the value option, however that jira field (Affects versions) is not listing in the dropdown "Field to copy value from".

Screenshot 2024-12-04 at 14.17.20.png

Kai Becker

@Kemal Solmaz ok, so the problem here is, that only fields of the same type will be listed there. And as Affects versions is a multi select, it does not show up.

I would recommend the solution @Florian Bonniec provided:

Switch back to set instead of copy
use smart value from Affects versions (making sure there is only one value)
{{issue.Affects versions.last}}

Kemal Solmaz

That sorted the issue, thanks a lot.

Kemal Solmaz

Exactly, after this change automation worked as expected. Thank you.

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