Problem Definition:

      If we looked at the older JIRA Service Desk Marketplace listing before JIRA 7, it appears that JIRA 6.4.12~6.4.14 is not listed to be compatible with any JSD version. But, it seems that installing JIRA Service Desk 2.5.9 to JIRA 6.4.12 is possible and there is no functionality being lost.

      Suggested Solution:

      Update the page with the correct JIRA Service Desk version that is compatible for JIRA 6.4.12 to 6.4.14.

            [JSDSERVER-5144] No Compatible Version of Service Desk for JIRA 6.4.12~6.4.14

            Atlassian Update - 03 March 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Service Management Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 03 March 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact. We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Service Management Data Center

            To prepare one of my JIRA instances, I had to clear up the plugin caches but Jira Service Desk "disappeared"

            I manually updated the add-on version 2.5.9 for my JIRA Server v 6.4.12 and updating the license key looks to have restored functionality (before I can upgrade that instance to an Atlassian-supported version)

            Arraaf Mochny added a comment - To prepare one of my JIRA instances, I had to clear up the plugin caches but Jira Service Desk "disappeared" I manually updated the add-on version 2.5.9 for my JIRA Server v 6.4.12 and updating the license key looks to have restored functionality (before I can upgrade that instance to an Atlassian-supported version)

            Unfortunately I cannot confirm the workaround.

            Tried installing JSD 2.5.9 on JIRA 6.4.12 and it will be shown as incompatible.

             

            This is probably an edge case and of minor importance.

            Christopher Mohr added a comment - Unfortunately I cannot confirm the workaround. Tried installing JSD 2.5.9 on JIRA 6.4.12 and it will be shown as incompatible.   This is probably an edge case and of minor importance.

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: