Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Best practice - offboarding Jira Service Management Customers. Delete or Revoke? Edited

Our Jira Service Management project is an internal Service Desk. I want to understand what the best-practice is when we are offboarding staff who have left the business. Should we a) Delete the account or b) Revoke the access?

 

I understand Delete is removing the account but will all tickets stay in the system for record/reporting purposes? If so Delete sounds good. I would assume Revoke is only going to be if there is a chance we need to re-enable the person in the future. 

If I delete can I add the same e-mail address again in the future? (albeit without the new account having access to the old account's history.)

 

1.png

 

Thanks for any clarity you can give me on this.

1 answer

1 accepted

3 votes
Answer accepted

Hi @Jeff Wynne ,

i feel like revoke is the best option here.

Delete will really remove the account so 99% sure the history will also be gone. Haven't had a need to re-invite someone that created a new account on an "old" email but since internally they have a long account id (like a guid) I fear the new account might have another one.

Going by this article some information is retained but they will show as "Former User" if you delete them.

https://support.atlassian.com/jira-cloud-administration/docs/deactivate-or-delete-managed-accounts/

 

Like the articles says, start with revoke to be safe, you can always delete later on:)

Thank you @Dirk Ronsmans - very helpful. I think just based on the screenshot in that article which shows the 'former user' replacement text, it's going to make sense to go with Revoke rather than Delete. I will want the reporter name along with the issue itself for historical records. 

Thanks again! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Service Management

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

682 views 10 15
Read article

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