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

Upgrade from JIRA 7.0 to latest JIRA version with JRASERVER-59812 Bug Fix Did Not Fix Those Lost Dashboard Gadget configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Low Low
    • None
    • 7.0.0, 7.0.11, 7.8.2, 7.13.0
    • Dashboard & Gadgets
    • 7
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 25-01-2019

      Hello everyone,

      I’d like to follow-up on concerns regarding the issue as it raised disappointment among customers impacted by the issue. That’s why the team is elaborating on reasoning behind the decision.

      While the bug is painful for larger customers, the amount of customers impacted by the issue through the years is low. Based on the amount of customers and upgrade patterns, the projected number of instances that might be affected by the issue is also low. We believe Atlassian Support can provide guidance for those customers. To our best knowledge, the Gadget configuration would be lost or corrupted during the migration from 6.4 to 7.0. Because of this, we recommend to create a Jira XML Backup on version 6.4 (or earlier). Atlassian Support and engineering team would then use the backup to attempt to restore the lost or corrupted configurations.

      From the technical perspective - the issue is affecting customers who are upgrading from Jira version 6.4 onto newer versions. Upgrade through 7.0 version is mandatory. Both versions have reached their end of life - so Atlassian is no longer issuing the releases (Jira 6.4 has reached End Of Life on March 17th 2017, Jira 7.0 has reached End Of Life on October 6, 2017).

      Jira Server Development team instead would be working on areas of bigger impact, that we believe bring more value for larger number of customers (if not all customers). Please follow our newly created bugfix dashboard to see issues we are going to work on soon and issues that have been shipped recently.

      Cheers,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 25-01-2019 Hello everyone, I’d like to follow-up on concerns regarding the issue as it raised disappointment among customers impacted by the issue. That’s why the team is elaborating on reasoning behind the decision. While the bug is painful for larger customers, the amount of customers impacted by the issue through the years is low. Based on the amount of customers and upgrade patterns, the projected number of instances that might be affected by the issue is also low. We believe Atlassian Support can provide guidance for those customers. To our best knowledge, the Gadget configuration would be lost or corrupted during the migration from 6.4 to 7.0. Because of this, we recommend to create a Jira XML Backup on version 6.4 (or earlier) . Atlassian Support and engineering team would then use the backup to attempt to restore the lost or corrupted configurations. From the technical perspective - the issue is affecting customers who are upgrading from Jira version 6.4 onto newer versions. Upgrade through 7.0 version is mandatory. Both versions have reached their end of life - so Atlassian is no longer issuing the releases (Jira 6.4 has reached End Of Life on March 17th 2017, Jira 7.0 has reached End Of Life on October 6, 2017). Jira Server Development team instead would be working on areas of bigger impact, that we believe bring more value for larger number of customers (if not all customers). Please follow our newly created bugfix dashboard to see issues we are going to work on soon and issues that have been shipped recently . Cheers, Ignat Alexeyenko Jira Bugmaster

      Issue Summary

      Due to the bug reported in JRASERVER-59812, when we upgrade from JIRA 6.4 to latest JIRA Version with JIRA 7.0 as the intermediate version. We will hit into JRASERVER-59812 bug which causing gadget preference goes wrong. Although it was being fixed in JIRA 7.6.6, 7.7.4, 7.8.2, 7.9.0 onwards, upgrading from JIRA 7.0 XML backup to a fixed version user will still encountering the same issue as JIRA 7.0 XML containing wrong gadget preference details.

      Environment

      JIRA 7.0.x, JIRA 7.8.2, JIRA 7.13

      Steps to Reproduce

      1. Reproduce the behavior in JRASERVER-59812 ticket in JIRA 7.0
      2. Upgrade to JIRA 7.8.2 or JIRA 7.13
      3. Access to the gadget and you shall see the issue persist

      Expected Results

      Upgrade to a fixed version, wrong configurations gadget details shall be fixed accordingly.

      Actual Results

      Once we upgrade from an impacted JIRA version to a fixed JIRA version, the issue remains as XML backup/database generated from older JIRA Version was having wrong configurations such as preference.

      2018-12-21 23:53:00,085 http-nio-8080-exec-3 WARN rhaverin 1432x406x1 1hrivnx 0:0:0:0:0:0:0:1 /rest/dashboards/1.0/13152/gadget/17625/prefs [c.a.jira.dashboard.JiraDashboardStateStoreManager] Stored state for dashboard with id '13152' is not the same as in-memory state. Trying to rewrite the entire state...
2018-12-21 23:53:00,477 pool-14-thread-1 INFO jiraadmin 1429x132x1 1l1ep0s 0:0:0:0:0:0:0:1 /plugins/servlet/embedded-crowd/directories/disable [auditorlog] Event{author=rhaverin, ipAddress=0:0:0:0:0:0:0:1, category=Dashboards, summary=Gadget configuration edited, object=MS6 Guarantee Basic, details=[EventDetail{name=Dashboard name, value=MS6 Guarantee Basic}, EventDetail{name=Gadget name, value=Pie Chart}, EventDetail{name=Gadget url, value=rest/gadgets/1.0/g/com.atlassian.jira.gadgets:pie-chart-gadget/gadgets/piechart-gadget.xml}, EventDetail{name=projectOrFilterId, oldValue=filter-11441, newValue=null}]}

      Notes

      Upgrade from JIRA 6.4 to any latest JIRA Version will require to go through JIRA 7.0.x due to JIRA Agile and JIRA Service Desk minimum requirement.

      Workaround

      Reconfigure the dashboards

              Unassigned Unassigned
              dkoh Danson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: