Development
Sort by:
Trending
Status:
Future consideration
Showing 134
4
VOTE
Maintain cycle time data when team workflow is changed
Currently if I select a new workflow for my team and map my statuses to new statuses, I lose all past cycle time data because cycle time only focuses on the current workflow being used. Instead, I would like to see historical data that coincides w...
0
Future consideration
2
VOTE
In Develop, allow items imported from dev tools to be added to Product work
Who would benefit? Users who receive product requests via GitHub or similar What impact would it make? It would allow to add both Product- and Engineering-related items from importer extensions How should it work? When dragging an item from the im...
0
Future consideration
20
VOTE
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...
2
Future consideration
1
VOTE
Allow Team to be set at the Release level
What is the challenge? We cannot associate a Release with a Team What is the impact? We cannot do necessary analysis in assigned Releases, commitment and deadline scores etc - stuff outside of Capacity. Describe your idea Allow the core Teams fiel...
0
Future consideration
2
VOTE
Retrospective should ignore records that were moved in with "Will not implement" status
Who would benefit? Product Owners and Project Managers What impact would it make? This would reduce the list of records shown as "incomplete" when the records were added to the release after already been assigned "Will not implement" How should it...
0
Future consideration
1
VOTE
Add a "create retrospective option" to develop
What is the challenge? Having retrospectives is an important scrum practice, at the moment it's pretty manual. go to documents create a whiteboard add a copy of the end of sprint review insert a retrospective template. What is the impact? It's jus...
0
Future consideration
1
VOTE
Add a throughput report to help Kanban teams with Service Level Estimates
What is the challenge? There currently is no way to calculate SLEs inside of Aha!. What is the impact? I have to export the data to a spreadsheet and then calculate it myself. Describe your idea Add a report that looks at team performance and calc...
0
Future consideration
1
VOTE
Add automated capacity planning to sprints
What is the challenge? People are notoriously bad at estimating, points or hours are equally bad, and often people feel pressured into lower estimates, making the problem worse. What is the impact? Accurate sprint planning is hard to do and repeat...
0
Future consideration
1
VOTE
New requirements that are created under a parent feature that is already in the prioritized backlog should automatically be placed in the prioritized backlog.
What is the challenge? New requirements that are created under a parent feature that is placed in the prioritized backlog is placed in another area of the workboard. The user then has to find the new requirement and move it to the prioritized back...
0
Future consideration
1
VOTE
Move the location of the "Hide Completed records" on the sprint planning page
What is the challenge? Currently it's under the people on the team and it's not where you look for that sort of feature. What is the impact? Sometimes you forget where it is. Describe your idea Move it to the top of the page and make it more promi...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved