Jira still record the changes in the history even the UserPicker (Multiple User) fields are null

[Ysaac James Salao]

Hi,

I have a transition screen where there are different field types in it. I noticed that even the UserPicker (Multiple User) fields are null it will still record the changes in history. 

Is there a way to avoid this?

[Nic Brough -Adaptavist- · Accepted solution]

No, these should be in the history, or you can't tell when the field was emptied out.

[Ysaac James Salao]

No updates have been made when I transitioned the button just to test it but these fields are still appearing in the History tab.

The reason why I would like to avoid this from happening is Jira fires an Issue Updated event when it occurs.

See sample screenshots below

[Andrew Laden]

Are you sure that isn't the event from the transition?

Also, do you have some scripting or automation that might be affecting those fields as a response to the transition?

[Nic Brough -Adaptavist-]

Thing is, the issue IS being changed.  It is having the fields blanked out (which you want your history to record). 

If you don't want the field changes written into the history (which does not actually have anything to do with the issue updated event, other than they're done as part of the transition), then you need to remove or prevent whatever is blanking them out. 

If the fields are on the transition screen, consider removing them so that your people do not get the chance to change them.  If they are being blanked out by a post-function, remove the post-function from the workflow.

[Ysaac James Salao]

Hi,

I'm using a post-function addon to copy the value from Project 1 to Project 2 - 5.

I was able to resolve the issue by just ticking the Ignore empty values where it doesn't set (clear) the field if the value from the current issue is empty or null.