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?
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)?
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.
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.
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.
It looks like you're new here. Sign in or register to get started.
