History lost when reporter leave the company

[Jirong Hu]

Our user is reporting the following issue. Any idea how this could happen?

Thanks

Jirong

~~~~~~~~~~~~

Over time tickets need to be updated with new priorities, or additional changes however if the "reporter" is someone that is no longer with the company the system will not let you save the changes until you replace the reporter with someone who is still in the system. As a result the entire history of the ticket is altered to show the new reporter as the one who made all the comments in the ticket and reported the issue.

This is a problem because the information of where the issue came from is lost. Currently I am just putting myself as the reporter so the priorities can be updated. But this posed problems because others reading the ticket assume I was the one that logged the issue.

The system should not alter historical comments, or require the original reporter to be changed when making updates to tickets after the person has left the company. This also skews reporting on tickets logged by person.

[Nic Brough -Adaptavist-]

It's because you are deleting the old users.  That is not what Atlassian recommend when someone leaves.

Stop deleting the users, and just deactivate them instead.

[Jirong Hu]

Our domain controller has confirmed the following procedure: when a user leaves the company, their account will be removed from all groups and deactivated, then after 90 days, will be deleted. We can't change their policy, so what's your suggestion?

[Nic Brough -Adaptavist-]

Stop deleting the users. You're destroying audit information.

[Mark Thompson]

@Nic Brough -Adaptavist- - We are not deleting users.  We just remove their site access and the user is removed as reporter on all their existing tickets.  We don't even take away group controls.  Just disable site access so there is a problem here.  At least that is what I see in the new view.

[Nic Brough -Adaptavist-]

If you just disable them, nothing will change in Jira (except that they can no longer be selected in the fields).   Exisiting data will not be removed or changed.  People will not be removed as a reporter unless you explicitly change it to someone else, or completely delete the user.

[Mark Thompson]

Just to be clear:

1.  Navigate to Administration/users

2. A user who is visible in this area with no site access is not deleted

Assuming above is correct:

1.  None of these users in our installation display as a reporter

2. None of these users are available as a selection when performing a query

[Nic Brough -Adaptavist-]

Yes, that's correct.  When someone who has reported an issue is inactive, they appear in the history and the reporter field, but you can not select them as a reporter of a new or edited issue.

[Mark Thompson]

I'll see what support has to say.  This doesn't look right to me.