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

Multiple Issue Picker is Firing Updates

Marcos Fernando Simon

Hi,

I'm facing an issue with the Multiple Issue Picker field type. I don't know if that's a bug or I'm doing something wrong.
I've added a Multiple Issue Picker field without any JQL or default issue. The field would be used to track the issues that caused a problem.
The thing gone wrong when I added an epic to the issue. Then, in the history tab, two lines appeared: one telling me that I changed the issue epic field (and that's correct) and another one for the Multiple Issue Picker field, that I haven't even touched! The field was indeed empty. If it's populated, then everything runs fine.
This doesn't happen when I use the Single Issue Picker field and that's how I'm dealing with the problem.
This image might make things clearer. The thumbnails are off because this is my test environment. My Multiple Issues Picker fields are Origin Task/s and _STM.

Could you guys help me?

Here are some info about my environment:

Jira version: 7.7.4
Script Runner Version: 5.5.5

Thanks in advance.

Accepted answers

PD Sheehan

Just a shot in the dark here... but I wonder if this is because the issue was created before you added those custom field.

When you update the issue to change the epic link, the form also initialized the custom field with an empty array: changed from null to []

When you create a new ticket after those fields are fully rolled out, the custom field initialization will happen on the create event and those details don't show up in the history.

Perhaps this could be reported as a bug or enhancement suggestion to Adaptavist. It would be nice if those empty array values could be stored as an actual null value. Then those multi issue picker fields could be adjusted to support the JQL operator IS EMPTY (which I think is currently not supported).

All comments

PD Sheehan

Just a shot in the dark here... but I wonder if this is because the issue was created before you added those custom field.

When you update the issue to change the epic link, the form also initialized the custom field with an empty array: changed from null to []

When you create a new ticket after those fields are fully rolled out, the custom field initialization will happen on the create event and those details don't show up in the history.