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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

How to archive a ServiceDesk and keep old issues available to customers in ReadOnly mode

Hi all,

We are moving to a new organization of our ServiceDesks. Some ServiceDesks projects will be closed but we would like to keep the issues available to customers on ReadOnly mode :

- it should be no longer possible to create an issue in the desired SD. Ideally, the ServiceDesk should no longer appear in the Help Center

- it should be possible to see old issues in the "My Requests" list of the customers.

- issue should be readOnly for every body

I'm trying to define a permission scheme for that. It seems that I need to keep the Browse project permission to get the old issues available, but this permission makes also the project presented in the Help Center.

Does somebody know which permissions I have to set to cover my needs ?


1 answer

0 votes
Fahad Siddiqui Community Leader Oct 05, 2020

@Nicolas Boutet  please go through the below link may be it will help you to fulfill your requirement.

Thank you. The link is talking about a ReadOnly for the entire site. It's not my need as I'm still using the same site for new ServiceDesk projects, and for other Jira projects!

Thank you again Fahad !

Your links are helpful. I found them as well, but unfortunately, I was not able to find there any response to cover my need.

Maybe I can try to reformulate more precisely what I'm trying to setup:

How to adjust the permissions scheme of a ServiceDesk project to get it hidden in the HelpCenter (customers portal), while keeping the old corresponding issues available to customers in ReadOnly mode?

- Removing the issue creation and edition permissions, set the project in ReadOnly more, but keep it available in the Customer Portal

- Removing the "Browse Project" permission hides the project from the CustomerPortal, but the issues are also no longer available in the "My requests" list of the customers.

You seem to be more familiar than me about in the Atlassian Community Questions. Do you think I need to be more precise in my initial question, or is it correct enough?

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

189 views 1 6
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