Loading...

XML

Word

Printable

Type: Suggestion
Resolution: Fixed
Fix Version/s: 6.1.2
Component/s: None
Labels:
None

Feedback Policy:

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.

There will be an Epic Report with three sections:

1: Epic progress chart
- Starts at epic creation time
- finishes on current date
- line for issue count
- line for unestimated issue count
- line for total amount of estimated work (using selected estimation statistic)
- line for completed work (using selected estimation statistic)
- tooltips will be like the sprint burndown
- show non-working days markings

This means we have two vertical scales (count and estimate)

2: Summary of current epic status
- Looks like the current statistics in the plan mode

3: Table showing all issues currently assigned with the current status (done in ~~GHS-6616~~)

Testing Notes

Q: What happens with stories that were moved/deleted/converted to subtasks and vice versa, and how is this displayed in the table?
A: Not Answered

Q: Are there any maximums to the table length, in terms of issuekey/number of issues/etc? Can you break these limits?
A: Not Answered

Q: What if the Epic itself was closed/done then reopened? Is the report still available and is there any indication about this history?
A: Not Answered

Q: What if editing another issuetype into an epic or vice versa?
A: Not Answered

Q: Are reports generated dynamically?
A: Not Answered

Q: What happens if I visit the report URL for another non-epic?
A: Not Answered

details

JSWSERVER-7193 Javascript error when trying to render CFD chart

Closed

JSWSERVER-7191 Bugs are not consistently categorised as either Estimated or Unestimated

Closed

JSWSERVER-7195 Date picker and Refine appears on Epic Report when switching between CFD and Epic Report

Closed

JSWSERVER-7115 Switching between epic's in the epic report doesn't work

Closed

JSWSERVER-7178 y-axis ticks are not formatted correctly

Closed

JSWSERVER-7183 Superfluous information when estimate statistic is Issue Count

Closed

JSWSERVER-7184 No chart is displayed if all issues in epic are in unmapped statuses (on this board)

Closed

JSWSERVER-7186 Converting a story to a bug does not create scope change event for loss of Story Points

Closed

JSWSERVER-7187 Issue count delta on black and blue series is missing

Closed

JSWSERVER-7190 Opinion - Epic Report should not be available on Kanban boards

Closed

JSWSERVER-7096 Create Epic burndown chart

Closed

JSWSERVER-7107 Opinion - should we have a View "Epic" in Issue Navigator link at the top of the report?

Closed

JSWSERVER-7179 Opinion - should the 'zero' point on the x-axis be butted against the y-axis on the left side?

Closed

JSWSERVER-7181 Opinion - legend is unclear

Closed

JSWSERVER-7182 Opinion - suggest using different line style for the second y-axis (issue count)

Closed

JSWSERVER-7188 Strange browser history behaviour when viewing Epic Report

Closed

JSWSERVER-7189 Epic Report should be promoted in list of available charts

Closed

JSWSERVER-7192 Opinion - Tooltip collapsing not consistent

Closed

JSWSERVER-7202 Epic chart with single issue shows empty chart

Closed

mentioned in: Wiki Page Loading...

(14 details, 1 mentioned in)

Assignee:: Unassigned

Reporter:: Shaun Clowes (Inactive)

Votes:: 5 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 24/Oct/2012 6:25 AM

Updated:: 19/Sep/2019 5:59 AM

Resolved:: 17/Jan/2013 5:30 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates