Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

History lost when reporter leave the company

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




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.


1 answer

2 votes

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.

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?

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

@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.

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.

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

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.

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

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you