It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Multiple Issue Picker is Firing Updates


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.


1 answer

1 accepted

0 votes
Answer accepted

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).

Hey, thanks for the quick response.

Guess I'll open a ticket to Adaptavist then.

I managed to use a single issue picker so the problem doesn't happen and my users are happy with it.


Thanks again.

Hi @Marcos_Fernando_Simon 

Have you raised an Atlassian ticket regarding this issue? I would like to have the link so I could have an extra reference. 

Thank you!



Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you