Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4732

Add supported method for removing all JSD data from instance

    XMLWordPrintable

Details

    • 1
    • 36

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Atlassian Update - October 2023

      Hi Everyone,

      Thank you for previously raising this feature request and bringing it to our attention.

      Within our company roadmap and work capacity, we try to address or review each feature request but admit that not each one will be implemented. To continue the culture of being honest and open, we are closing this ticket to focus on our upcoming roadmap for all Jira Service Management Cloud users. You can visit Atlassian Cloud Roadmap to learn more about what was recently released and the upcoming roadmap.

      Thank you again for providing valuable feedback to our team!

      Anchal Chopra
      Jira Service Management Cloud team

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      Description of Problem:

      JIRA Server instances that have had JSD in the past may have trouble installing JSD 3.2+ if they ever had JSD in the past and did not go through JSD 3.0/3.1 to complete the necessary upgrade tasks.

      In some cases JSD data is unwanted and can be deleted. For example when JSD was previously installed as a trial.

      Suggestion

      Add a supported method for removing all JSD data from the instance.

      Use case and suggestion:

      1. Customer upgrading from JSD 2.5.9 or under and does not wish to keep any JSD data (JSD was a trial, or any other reason)
        • If desired, customer is able to remove all JSD data so that they can install JSD anytime in the future
      2. Customer who is currently running JIRA 7.2 and up and is trying to install JSD. Unbeknownst to the customer JSD was installed in earlier version and 3.0/3.1 upgrade tasks were not completed.
        • Customer is able to drop all JSD data so that they can install JSD without having to attempt downgrade.

      Suggesting adding a startup flag that tells JSD to drop all JSD data

      Workaround

      There is currently no supported workaround. Directly modifying the JIRA database to remove JSD data is not supported.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JSDSERVER-4732 Unable to install JSM if data exists from version prior to 3.2 upgrade steps

          • Highest - Our top priority issues
          • Closed

          Suggestion - JSDCLOUD-4239 As a JIRA Service Desk administrator, I would like to be able to upgrade from JSD 2.5.9 to 3.2 directly

          • Closed

          Suggestion - MP-75 Add ability to remove add-on / plugin / app data as well upon Uninstallation.

          • Gathering Interest

          JSMDC-541 Loading...

          Activity

            People

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              16 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: