Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36996

When upgrading JIRA from 5.0.7 to 6.1.7 using the installer in Windows, the service is renamed to default Atlassian JIRA

XMLWordPrintable

      When you upgrade JIRA 5.0.7 to 6.1.7 using the Windows installer, and you have JIRA installed as a service, the service automatically gets renamed to "Atlassian JIRA".

      This doesn't happen when upgrading from:
      5.0.5 to 6.1.7
      6.1.5 to 6.1.7
      So it must be specific to JIRA 5.0.7 where it happens.

      WORKAROUND:
      Manually reinstall the service.

            [JRASERVER-36996] When upgrading JIRA from 5.0.7 to 6.1.7 using the installer in Windows, the service is renamed to default Atlassian JIRA

            Aakrity Tibrewal added a comment -
            Atlassian Update - 10 April 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.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

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

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 10 April 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. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Data Center

            Taiwo Akindele (Inactive) added a comment -

            We managed to reproduce this problem of a new service with "Atlassian JIRA" being created when testing upgrades of JIRA services in windows with a variety of versions actually including upgrade from 6.1.7 to 6.4.7. It's not clear if there are some versions that are not affected.

            Taiwo Akindele (Inactive) added a comment - We managed to reproduce this problem of a new service with "Atlassian JIRA" being created when testing upgrades of JIRA services in windows with a variety of versions actually including upgrade from 6.1.7 to 6.4.7. It's not clear if there are some versions that are not affected.

              Unassigned Unassigned
              dleng Daniel Leng (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: