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

Moving issues to different project causes issues with Velocity charts.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 9.6.0, 9.4.2, 9.4.7
    • Project - Agile Boards
    • None

    Description

      Issue Summary

      When all issues are moved from Project A to Project B, the Sprint details and the Sprint reports get moved with the correct data. However, the velocity chart fails to read the data and produces wrong/empty data.
       
      This is reproducible on the Data Center: yes

      Steps to Reproduce

      1. Create 2 projects (Project A and B) and have 4 or more issues in Project A
      2. Create 2 Sprints in Project A and add issues to each Sprint.
      3. Add some random story points and complete the Sprints
      4. Validate the reports (mainly the Velocity chart)
      5. Move the issues from Project A to Project B.
      6. Validate the Sprint report, the dates will be correct
      7. However, the Velocity chart will not show any data. No Committed or Completed points will be seen. The report will be empty.

      Expected Results

      The velocity chart to read the data form the history of the issue and from the Sprint data to populate the data correctly.

      Actual Results

      The velocity chart shows incorrect information.

      The sprint report will still have the correct information


      Workaround

      Currently, there is no known workaround for this behaviour. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              f956e0e022e9 skavatekar
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: