Can we OFF Jira Service Desk (Cloud) from Atlassian Access for few months and ON later?

Divya Rani Bazar September 9, 2019

Planning to OFF Jira Service Desk (Cloud) from Atlassian Access for few months and ON later. Would like to know if existing service desk projects can be accessed after OFF and ON of Jira Service Desk (cloud) or will lose service desk projects immediately after OFF. 

Do we have a workaround such as to maintain backup of service desk projects before OFF and later retrieve the projects upon ON. 

1 answer

1 accepted

1 vote
Answer accepted
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 11, 2019

Hello Divya, 

Thank you for contacting us about this.

Once you delete a product from your Cloud instance, the data is permanently removed.

See Reset and Delete All Data from Your Cloud Site:

Once you delete a cloud product, all data and settings associated with that product are deleted immediately. Reactivating the product will not recover the data, and we can’t recover your data for you. This does not affect user management or your users' Atlassian accounts; they will not be deleted through this process.

We recommend creating a Confluence site backup or Jira site backup before resetting your products to avoid accidental data loss.

You can find more information about how we store and manage your data on our data storage FAQs.

You can attempt to migrate your Jira Service Desk issues to a Jira Core project by using the procedure available at JIRA Software : Moving JIRA Software project to Service Desk

Note: Although the above procedure refers to Jira Software to Service Desk migration, the procedure is the same, except you'll be creating a new Jira Core project instead of a JSD project.

This procedure is not supported or recommended to do if you have existing issues in the project.

By migrating, your SLA will be lost, CSAT, and likely your request types. You will likely lose data in this process should you need to move it back to Jira Service Desk.

I hope that clarifies things, but do let me know if you have any further questions.

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer