-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
2
-
There is no easy way at the moment to see the size of the backlog in story points, and progress towards it from a project perspective.
The velocity charts in the Reports tabs are nice, but since we release at the end of each sprint, and have to use the Version field to store the release number, we can't use the velocity charts to show a picture of the whole project.
I'd like to see either:
- Another option on the Version Report to show "All" - i.e a single burnup chart regardless of version
- An additional tab on "Reports" that says "Projects" and allows you to see the burnup for an individual project, or multiple projects (i.e. the ability to multi-select from the list of projects that are included in your filter)
Note that this is distinct from GHS-5513, which relates to sprint level burnup charts (although many of the comments there are complaining of a lack of a project level view)
- relates to
-
- Closed
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-10493] As a Product Owner, I want to see a burnup chart for the Project (not sprint or version)
Toby Jackson
added a comment - We create sprints using labels from multiple project sources - "Application support", "Infrastructure", "Product X" "Project Y" etc, and whilst I'd like to use fixVersions as most of JIRA/Agile/Confluence user this as pivots for reporting due to JRA-2698 we're unable to have common versions across the projects.
This story would allow us to generate reports based on sprints without any consideration to fixVersions; it seems all the release burnup requires is a start and end date, or perhaps a list of sprints that are included in the view?
Toby Jackson
added a comment - We create sprints using labels from multiple project sources - "Application support", "Infrastructure", "Product X" "Project Y" etc, and whilst I'd like to use fixVersions as most of JIRA/Agile/Confluence user this as pivots for reporting due to JRA-2698 we're unable to have common versions across the projects.
This story would allow us to generate reports based on sprints without any consideration to fixVersions; it seems all the release burnup requires is a start and end date, or perhaps a list of sprints that are included in the view? +1
tl;dr; https://confluence.atlassian.com/display/AGILE/Labs+-+Viewing+the+Release+Burndown - this by with a filter/JQL query
We use version very similar to Mark, so the current implementation of the release burndown chart is pretty much useless to us. I really like the idea of instead of having the report based on a release, we could pick a filter or enter a JQL query and it would calculate the same report for us.
Tys von Gaza
added a comment - - edited +1
tl;dr; https://confluence.atlassian.com/display/AGILE/Labs+-+Viewing+the+Release+Burndown - this by with a filter/JQL query
We use version very similar to Mark, so the current implementation of the release burndown chart is pretty much useless to us. I really like the idea of instead of having the report based on a release, we could pick a filter or enter a JQL query and it would calculate the same report for us.
Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.
Regards,
JIRA Agile Team
Yes, please make it possible to generate this report based on the board's underlying JQL (i.e. "All" in the Version drop-down) or create a dashboard gadget that takes a filter as a parameter.