-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
The new version of GreenHopper is awesome, however it's missing Release planning and reporting functionality or am I missing it? In previous versions we could associate sprints to a "Parent" release, though thats no longer available if using a Scrum Board. The Sprint burndown and end of sprint reports are great, I'd like to see something similar for Releases.
For Example:
- Release burndown chart by project, sprints, hours, story points and/or issues: The chart should allow me flip back and forth between different views right on the screen without a need for Admin permissions to change or access to the scrum board configuration settings.
- The Release and Sprint burndown charts should be viewable on the dashboards
Question:
- Will the "Release" pull from the FixVersion field? If so, I'd like to suggest when building a Release I should be able pick from multiple projects and sprints. This might require an option to share a FixVersion across multiple projects.
[JSWSERVER-7741] As a User, I would like Release related reports & charts
Karie Kelly
added a comment - We would need the associated gadgets to migrate to this. The Classic allows us to input the start and end dates for the version and you need to be able to assign any items in JIRA to a version, not just do this in a sprint board. Currently, Greenhopper is requiring the use of scrum boards for everything; however, much planning is done outside of a scrum board, often with a kanban board or some other type of mechanism. These issues are then associated with a version for affinity planning and scoping of the version.
Often then a scrum board is created with a filter to only bring in items ready to be included in a sprint (e.g. a backlog of groomed stories). So, we don't want only those items assigned to that version to be those on a scrum board.
That is the value of the classic boards. You have start and targeted release date and all issues associated with that version, regardless of whether they have made it into the sprint or the sprint backlog.
Karie Kelly
added a comment - We would need the associated gadgets to migrate to this. The Classic allows us to input the start and end dates for the version and you need to be able to assign any items in JIRA to a version, not just do this in a sprint board. Currently, Greenhopper is requiring the use of scrum boards for everything; however, much planning is done outside of a scrum board, often with a kanban board or some other type of mechanism. These issues are then associated with a version for affinity planning and scoping of the version.
Often then a scrum board is created with a filter to only bring in items ready to be included in a sprint (e.g. a backlog of groomed stories). So, we don't want only those items assigned to that version to be those on a scrum board.
That is the value of the classic boards. You have start and targeted release date and all issues associated with that version, regardless of whether they have made it into the sprint or the sprint backlog.
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center