"assignee" unassigned after editing an incident

[Leo Lopez]

When the user changes any field in one incident, the incidents is automatically unassigned. The incident status isnt relevant, it happens all the time in any status. It is only happening to one particular user. Any idea? thanks

[Craig Haynal · Accepted solution]

Does the user have the Assignable User and Assign Issues permissions for the project?  Typically these would be granted through project roles.

Alternatively, is it possible the user has some kind of browser autofill feature emptying the field?

[Leo Lopez]

i will check tomorrow and i will let you know , thx

[Zita Bagi]

Hi, possibly there is a post-function in the workflow. Please go to project settings > workflows > select the workflow > edit > click on the given transition(s) > Post Functions, and check if there is anything which changes the Assignee. Maybe this person has a different type of permission to which the post-function applies.

Let us know if that's the case.

[Leo Lopez]

let me check, thx

[Leo Lopez]

the problem is that you dont need to move to another status to face the error, you just edit one field (without changing status) and the incidents is automatically unassigned, so transitions are not actually the problem. I also checked the user rights and it is exactly the same as all the other users (all others are not having this issue). It would say it is a bug in jira

[Zita Bagi]

Is there Adaptavist ScriptRunner in your Jira? What I can think of is there is a script somewhere in the background, maybe a Script Field for the user, a user group, is for the field.

[Leo Lopez]

im gonna google that, thx

[Leo Lopez]

no scripts, thx

[Leo Lopez]

i logged-in with the user in my laptop and the problem does occur so it is indeed something linked to the user's browser. i keep investigating with autofill features, thank you all for your quick and efficient support

[John Funk]

Hey Leo - have you looked at the history on the issue to see if it gives a clue about "who" changed the value? Do you even see the field getting cleared? 

I suspect there is some other script running like Z B said - either ScriptRunner or Automation For Jira or something like that. 

[Leo Lopez]

the history reads that the user removed the assignee, when it is not true. There is no Script runner or automation running, it is just basic cloud configuration with workflow and statuses. another idea?