Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-4259

Issue Burndown Chart incorrect after import issues from CSV

XMLWordPrintable

      Steps to reproduce:

      1. JIRA imports the issues from CSV and sets the status to closed.
      2. There is no history on the issue showing a status change from Open to Resolved, or something similar
      3. GreenHopper scans for status changes in the history, finds none and assume it's still Open, therefore does not mark it as Done
      4. Re-opening an issue means GreenHopper sees that re-opening as a +1 to the number of issues that are not done (because it went from Done to Not Done)
      5. Closing it again will then mean that GreenHopper simply does a -1 to burn down, but is only taking away the +1 it added on the re-opening

      Workaround
      Use Project Import functionality to import the project and issues to JIRA

            [JSWSERVER-4259] Issue Burndown Chart incorrect after import issues from CSV

            Bugfix Automation Bot made changes -
            Minimum Version New: 5.07
            Sergey made changes -
            Description Original: *Steps to reproduce*:
            # JIRA imports the issues from CSV and sets the status to closed.
            # There is no history on the issue showing a status change from Open to Resolved, or something similar
            # GreenHopper scans for status changes in the history, finds none and assume it's still Open, therefore does not mark it as Done
            # Re-opening an issue means GreenHopper sees that re-opening as a +1 to the number of issues that are not done (because it went from Done to Not Done)
            # Closing it again will then mean that GreenHopper simply does a -1 to burn down, but is only taking away the +1 it added on the re-opening

            *Workaround*
            Use [Project Import|https://confluence.atlassian.com/adminjiraserver071/restoring-a-project-from-backup-802592982.html] functionality to import the project             		New: *Steps to reproduce*:
             # JIRA imports the issues from CSV and sets the status to closed.
             # There is no history on the issue showing a status change from Open to Resolved, or something similar
             # GreenHopper scans for status changes in the history, finds none and assume it's still Open, therefore does not mark it as Done
             # Re-opening an issue means GreenHopper sees that re-opening as a +1 to the number of issues that are not done (because it went from Done to Not Done)
             # Closing it again will then mean that GreenHopper simply does a -1 to burn down, but is only taking away the +1 it added on the re-opening

            *Workaround*
             Use [Project Import|https://confluence.atlassian.com/adminjiraserver071/restoring-a-project-from-backup-802592982.html] functionality to import the project and issues to JIRA
            Sergey made changes -
            Description Original: *Steps to reproduce*:
            # JIRA imports the issues from CSV and sets the status to closed.
            # There is no history on the issue showing a status change from Open to Resolved, or something similar
            # GreenHopper scans for status changes in the history, finds none and assume it's still Open, therefore does not mark it as Done
            # Re-opening an issue means GreenHopper sees that re-opening as a +1 to the number of issues that are not done (because it went from Done to Not Done)
            # Closing it again will then mean that GreenHopper simply does a -1 to burn down, but is only taking away the +1 it added on the re-opening             		New: *Steps to reproduce*:
            # JIRA imports the issues from CSV and sets the status to closed.
            # There is no history on the issue showing a status change from Open to Resolved, or something similar
            # GreenHopper scans for status changes in the history, finds none and assume it's still Open, therefore does not mark it as Done
            # Re-opening an issue means GreenHopper sees that re-opening as a +1 to the number of issues that are not done (because it went from Done to Not Done)
            # Closing it again will then mean that GreenHopper simply does a -1 to burn down, but is only taking away the +1 it added on the re-opening

            *Workaround*
            Use [Project Import|https://confluence.atlassian.com/adminjiraserver071/restoring-a-project-from-backup-802592982.html] functionality to import the project
            Sergey made changes -
            Affects Version/s New: 7.11.2 [ 81100 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2855323 ] New: JAC Bug Workflow v3 [ 2933563 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2540060 ] New: JAC Bug Workflow v2 [ 2855323 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1545949 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2540060 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 905218 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1545949 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 742381 ] New: JIRA Bug Workflow w Kanban v6 [ 905218 ]

              Unassigned Unassigned
              klfoong Foong (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: