JIRA user left the company (now inactive user), and now I can't edit the issue where he is the reporter.

[Roman Serazhiev]

User left the company, and we have the ticket which was reported by him.

I wanted to edit the description, but the red text appeared when I tried to save it: "The reporter specified is not a user."

I tried to do that on our TEST env with another non active reported in another project, and I was able to do that even though both assignee and reporter are inactive.

What's the difference? How to make the same thing on another instance? I want to be able to edit issue where Reporter and assignee are inactive.

P.S. Please, do not offer to change the reported. We don't want that as we need to keep the history who reported the issue without going though the activity tab.

Thanks.

[Roman Serazhiev · Accepted solution]

Atlassian Support (3rd level actually) were able to identify a bug, that when a user is created using mixed-case (e.g. AquaMan), and if this user is no longer active, then editing doesn't work.

JIRA issue: https://jira.atlassian.com/browse/JRA-38412

Workaround: use inline edit.

[Marc Jason Mutuc]

You can try editing the description via Bulk Edit. Just make sure you have the correct permissions.

[Roman Serazhiev]

Hi Marc,

That is not exactly what I want. I want to be able to edit the single issue where the reported is inactive. The thing is that I can on TEST env, but can't on PROD, even though TEST is a copy of PROD (only not recent). Is there some setting/premission that doesn't allow me to do it on PROD?

Thanks.

Roman.

[Marc Jason Mutuc]

Yes... probably. Could you look into the Permission Scheme applied to the Issue's Project?

[Roman Serazhiev]

The permission scheme is OK. The inactive user is still in two admin groups, he is an assigneable user and so on.

Also, I don't know it that would help or not, but this user can be found in Users in JIRA, but I cannot assign anything to him. It just won't show up when I start tyoing his name. I agree it should be like that, and the same happens on another env we have. But on another env, I can modify the issue leaving the inactive user as a reporter ans assignee.

[Mark MacVicar]

I had a related issue that I couldn't resolve an issue with an inactive reporter. Bulk Edit worked around it.