Analytics and Reporting are part of Develop Advanced, and users in those accounts are able to save list reports. However, some teams use list reports as part of their backlog and sprint management process. They don't need sophisticated analytics, ...
Some development teams use a scoring system for prioritizing their backlog. Teams using Aha! Develop with Aha! Roadmaps have access to this scoring functionality, but teams on Develop Essentials do not. Add support for Aha! Scorecards to Develop E...
Jeff Tucker
over 3 years ago
in Sprints
1
Future consideration
Ability to bulk change the team status on features or requirements
Sometimes a feature ships but some of its requirements are not marked as done by the developer. Currently we need to manually update the status on each requirement's page in order to stop it from displaying in the backlog.
Kelly Sebes
over 3 years ago
in Sprints
0
Future consideration
Ability to Toggle Requirements off and on for Sprint Planning
There is currently a checkbox to hide completed items on the sprint planning board. It would be great for a checkbox bellow it that would hide requirements and only show the current features in play for times when a feature has multiple requiremen...
Justin Paulson
over 3 years ago
in Sprints
2
Future consideration
Capacity for teams is currently available to set up at a daily, weekly, monthly and quarterly. It would be helpful for teams that are planning sprints, to be able to set a capacity for each item (Theme/epic/feature) per sprint. Once this is done, ...
samir karandikar
about 4 years ago
in Sprints
3
Future consideration
Burn *Up* charts for Sprints, Releases, Epics, and Features
My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature For more on the requirements for a Burn Up chart and why it is more useful than a Bur...
Mark D
over 7 years ago
in Releases / Sprints
2
Future consideration