A custom single selection user picker is causing multiple fields to be removed when users change?

[Alexander Rosado]

In certain cases that are difficult to track, the same 6 fields get removed when a user is changed in a custom user picker.  There is no background logic found that can contribute to this behavior. Does anyone know the reason of this bug?

[Nic Brough -Adaptavist-]

What do you mean by "fields get removed"?  The data in them is deleted?  Or they vanish from the screen when you change the user selected (if that, then do they come back if you reselect the old user)?

[Alexander Rosado]

The data in them get deleted.  That is the terminology used in the activity section. It does not happen consistently either.  There are random occurrences of it taking place. It only affects one project.

[Nic Brough -Adaptavist-]

Normally Jira will record a field as "cleared" rather than deleted.  But that's an aside, probably cosmetic and not helping as an answer.

Unless your human is actively blanking out the fields at the same time as editing the content of the user-picker, the only thing here is an automation of some sort that is catching "edit" and blanking the fields for you.

You will need to check all the automations, scripts, listeners and apps - someone has created an process that is catching the field update and killing off the other field data.

[Alexander Rosado]

I double checked all the logic affecting the fields. Most logic sets specific fields to required depending on status. There is logic that sets the reporter to the custom user picker during a transition. Some logic that checks if fields are empty, but none of the behaviors, conditions, post functions or listeners that erases data.

[Nic Brough -Adaptavist-]

Ok, there is  nothing in Jira that will do this natively, it has to have been created by an admin with an automation, listener or function of some sort.

I'd want to look at the issue history more closely.  Exactly what action is the deletion being done by?  Edit, transition, or something custom?  Might it be an external REST call?  Which person is listed as having made the changes in the history?