Capacity planning
Sort by:
Recent
Status:
Future consideration
Showing 138
3
VOTE
Capacity report - do not show logged work on a view of initial estimates only
Who would benefit? When initial estimates are used for capacity, logged work on records does not adjust planned work accordingly and this causes an inaccurate capacity report. Removing logged work from initial estimate view of capacity report will...
0
Future consideration
3
VOTE
Limited layout functionality on capacity team record
Who would benefit? Users who would like to add custom fields to the account settings > capacity planning > teams view What impact would it make? Ability to add custom tabs and add rows to a custom table How should it work? When editing the l...
0
Future consideration
5
VOTE
Best estimate on epics is confusing when child feature estimates are not complete
Who would benefit? Situation: I am using the best estimate on an epic. The epic has 2 child features with no estimates. My epic is set to calculate detailed estimate from child features Result: The epic shows the detailed estimate as Σ0 and not bl...
1
Future consideration
6
VOTE
Ability to compute the Initial estimate of an Epic from Features estimates
Who would benefit? All PMs who require to see Initial estimates at both Epic and Feature level but don't want them to be double counted in the "Remaining Work" of a Release. Currently the "Features and epics" option of the Release "Use estimates f...
0
Future consideration
4
VOTE
Add delivery risk check for missing initial estimate
We use the initial estimate field for early product planning. While the "No detailed estimate" field helps for our detailed planning stage, we want similar functionality that checks for missing initial estimates to support our earlier planning.
0
Future consideration
2
VOTE
Capacity Planning Report: Add fields to Detail Portion of Report
We would like the ability to add a few fields to the detail view to help decide which Features/Epics we need to cut, renegotiate, or move to other teams. We have two custom fields that would be helpful to add here (Feature Priority and PI - Planni...
0
Future consideration
1
VOTE
'Add as logged time' setting only works on initial completion
Current behavior (working as expected): Create a feature in Aha! And send it to Jira Update the “Story Points” field in Jira to 10p which syncs back to Aha! Change the Jira Story status to ‘Done’ which syncs back to Aha! and updates the ‘actual ef...
0
Future consideration
1
VOTE
1
VOTE
1
VOTE
Allow breakdown by Team for Detailed Estimates
The Initial Estimate Field of Epics and Features allows breaking down the effort values by Team. However, the Detailed Estimate Field does not allow effort to be broken down by team. You can only enter a value, but you cannot assign it to a specif...
4
Future consideration