Uploaded image for project: 'JIRA Service Desk Server'
  1. JIRA Service Desk Server
  2. JSDSERVER-4732

Add supported method for removing all JSD data from instance



    • UIS:
    • Feedback Policy:
      We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? 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.

      Or, they might be able to install JSD 3.2+, but they won't be able to create any new Service Desk Project, and will see the following error in the logs:

      2019-01-29 02:14:05,217 JIRA-Bootstrap ERROR      [bootstrap.lifecycle.server.ServerPluginLifeCycle] '2.0.2' version of Service Desk cannot be upgraded to '3.9.2-REL-0010'. Upgrade to '3.0.0' <= <version> < '3.2.0' first.
      com.atlassian.servicedesk.bootstrap.lifecycle.server.UnsatisfiedVersionRequirementException: '2.0.2' version of Service Desk cannot be upgraded to '3.9.2-REL-0010'. Upgrade to '3.0.0' <= <version> < '3.2.0' first.
      	at com.atlassian.servicedesk.bootstrap.lifecycle.server.UpgradeRequirementsChecker.checkVersionRequirementForUpgrade(UpgradeRequirementsChecker.java:47)

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


      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


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


          Issue Links



              • Assignee:
                tevans Tim Evans
              • Votes:
                58 Vote for this issue
                57 Start watching this issue


                • Created: