Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-6616

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature 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

          1.
          		 Update preview text for Available Reports page Sub-task Closed Unassigned
          2.
          		 Some "done" issues are not showing up as "Completed" in the Epic report Sub-task Closed Unassigned
          3.
          		 Handling of "Issue Count" estimation statistic needs improvement Sub-task Closed Unassigned
          4.
          		 Style inconsistencies between Epic Report and Sprint Report Sub-task Closed Unassigned
          5.
          		 Opinion - epic query parameter should use issue key instead of issue ID Sub-task Closed Unassigned
          6.
          		 Lack of valid epic query parameter in browser address bar should force Report to insert a query parameter Sub-task Closed Unassigned
          7.
          		 Opinion - "View in Issue Navigator" links could be generated differently Sub-task Closed Unassigned
          8.
          		 Hacking the url does not work - it falls back to the previous selected epic key Sub-task Closed Unassigned
          9.
          		 JQL custom field names must not be hardcoded Sub-task Closed Unassigned
          10.
          		 Epic status report table shows issues which are in unmapped statuses Sub-task Closed Unassigned

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

                Created:
                Updated:
                Resolved: