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

Show table at bottom of single Epic report that shows the estimate (current) for Done, Undone - Estimated, and Undone - Not Estimated stories

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.1.2
    • None
    • 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.

      COS:

      • Similar to existing Sprint Report
      • Include key, summary and current estimate

      Testing Notes

      Q: What if issues are removed and readded to an epic?
      A: the report represents current state only

      Q: What happens to the table if there are negative estimates?
      A: same thing as sprint report

      Q: What if the epic is visible on the board, does not contain any issues on that board, but contains issues from another project? What will be displayed in the table?
      A: no issues - report is dependent on the board query

      Q: What if the estimation config is removed/modified from issues on the board?
      A: report represents current estimation config as per sprint report

            [JSWSERVER-6616] Show table at bottom of single Epic report that shows the estimate (current) for Done, Undone - Estimated, and Undone - Not Estimated stories

            Reopening due to concerns found.

            Michael Tokar added a comment - Reopening due to concerns found.

            Issue GHS-7107 will be done as part of GHS-6392

            JoanneA (Inactive) added a comment - Issue GHS-7107 will be done as part of GHS-6392

            I have raised some concerns against this – moving back to In Progress.

            Michael Tokar added a comment - I have raised some concerns against this – moving back to In Progress.

            Please test on branch GHS-6616-epic-report

            JoanneA (Inactive) added a comment - Please test on branch GHS-6616 -epic-report

            If you pick up this story, please ensure you complete the QUnit tests. Thank you

            JoanneA (Inactive) added a comment - If you pick up this story, please ensure you complete the QUnit tests. Thank you

            Partially completed, I will finish it off in the New Year if somebody else doesn't pick it up in the meantime.

            Done:
            ====

            • Created Epic report "page" within the reports
            • Display Epic Picker on page
            • Created REST endpoint for the report data
            • JavaScript created to query for list of epics and draw picker, then query for report - did not complete the processing of the data
            • JS updates the URL to show that we are viewing the epic report but doesn't store the currently selected epic
            • JavaScript test skeleton created and tests written for drawing the epic picker
            • Refactored charts to pull some common code into ChartView.js and ChartController.js

            Left to do:
            ===========

            • Process report data and draw tables (and complete tests for this)
            • Add a link to issue nav in the header
            • Draw the spinner when the page is loading (and complete tests for this)
            • Remember the last selected epic
            • Wire up dropdown events so that it actually works
            • Ensure there are no js errors when switching from plan to report view - there were some issues - also ensure "no sprints" or "no epics" info messages appear properly in this case

            JoanneA (Inactive) added a comment - Partially completed, I will finish it off in the New Year if somebody else doesn't pick it up in the meantime. Done: ==== Created Epic report "page" within the reports Display Epic Picker on page Created REST endpoint for the report data JavaScript created to query for list of epics and draw picker, then query for report - did not complete the processing of the data JS updates the URL to show that we are viewing the epic report but doesn't store the currently selected epic JavaScript test skeleton created and tests written for drawing the epic picker Refactored charts to pull some common code into ChartView.js and ChartController.js Left to do: =========== Process report data and draw tables (and complete tests for this) Add a link to issue nav in the header Draw the spinner when the page is loading (and complete tests for this) Remember the last selected epic Wire up dropdown events so that it actually works Ensure there are no js errors when switching from plan to report view - there were some issues - also ensure "no sprints" or "no epics" info messages appear properly in this case

              Unassigned Unassigned
              sclowes Shaun Clowes (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: