Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

End Date Customers tied to a Project

Mary Frize
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 2, 2024

HI - using Jira Service Management Support and I have a few projects that are no longer being utilized.   I want to end date the customers tied to these projects without losing the ticket history.

Is this a bulk change - so go to project settings - customers - find the user and click on the Open or Closed Requests and then do a bulk change?    I would want to change the Reporter to someone that should be active.

image.png

Make sure to not send the email (so do not check this box)

 

image.png

 

Can someone please confirm my thoughts here

 

Thanks

Mary 

1 answer

0 votes
Robert DaSilva
Community Champion
October 4, 2024 edited

Hi @Mary Frize , welcome to the Community!

I haven't seen the term "End Date" used in this context, could you elaborate on what you're intending to do? I am inferring that you mean to either remove access, or otherwise deactivate some of your customer accounts.

Are these customers "Internal" to your organization, or are they external users? 

Internal users can be fully deleted, and this is usually done if that person no longer works at your company.

External users can have their access removed from your specific instance.

 

Either way, when an internal user is deleted, or an external users' access removed, there is only minimal impact to their ticket data.

As far as I know, the only impact is for deleted users. All ticket data remains, but where that user was the "Reporter" or "Assignee", they will show up as "Deleted User" instead. You can read more about this in this Atlassian Documentation page

 

---- 

 

To address the Bulk Change question, you're pretty much correct on the process. There are some items to consider though:

  1. A bulk change applies to all issues that appear as part of an Issue Search. Make sure that you're extremely specific with the filters you're applying.
  2. Changing the reporter should modify the reporter on all tickets in your search.
  3. If you extend your search to the Assignee field, you'll want to make sure the person you want to put into this field has the "Assignable User" permission. This is a project level permission that restricts which users can be assigned to tickets.

 

Hope that helps!

Robert

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, confluence administration, confluence admin training, confluence learning path, manage users and permissions, confluence certification, atlassian learning, cloud admin tools, streamline collaboration, confluence admin best practices

🚨New Confluence Admin Course Alert!

Manage Confluence like never before! This new learning path teaches you how to manage content, users, and permissions while optimizing user experience. Built for admins at all levels who want to confidently lead and unlock more innovative collaboration.

Learn more
AUG Leaders

Atlassian Community Events