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

How to import an old sprint and produce sprint report?

XMLWordPrintable

    • 0
    • We collect Jira 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.

      I have data on an old sprint which was recorded in Excel. Now, I want to import the issues into JIRA and be able to view sprint reports of the same.

      I am able to view a burndown chart only when I change the scope of each issue, from 'To-do' to 'Done' or 'In progress'. The actual end date is way before the current date on which I changed the scope of the issues. But JIRA considers the current date (The day I change the scope of an issue) in the burndown chart.

      Is there a way, where I JIRA can consider the actual end date mentioned in my sprint data sheet so that I could import my old data and still produce valid reports.

       

            [JSWSERVER-15673] How to import an old sprint and produce sprint report?

            Tim Rooney added a comment -

            I can't believe there's no traction on this issue. We attempt to migrate folk often into DataCenter from past server implementations and we seem to always have to say to our customers, "Sorry, please use your Sprint Reports from the deprecated server for past Sprint oqe."  

            If we can import issues, assign them unique sprint numeric values, we should be able to enter a Start and End and Completion date in the import, so we truly migrate our users out of a legacy experience and fully adopt the new Jira environ.

             

            Tim Rooney added a comment - I can't believe there's no traction on this issue. We attempt to migrate folk often into DataCenter from past server implementations and we seem to always have to say to our customers, "Sorry, please use your Sprint Reports from the deprecated server for past Sprint oqe."   If we can import issues, assign them unique sprint numeric values, we should be able to enter a Start and End and Completion date in the import, so we truly migrate our users out of a legacy experience and fully adopt the new Jira environ.  

              Unassigned Unassigned
              076b20a7cd33 Krattika Talreja
              Votes:
              8 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: