Add Visual Effort Indicator to Features on Starter Roadmap
Our business stakeholders, rightfully so, need to understand the level of effort involved in the various items on our roadmaps. At the most basic level, this equates to showing them the number of developers involved in a given item (epic/feature),...
Capacity Report - pulling time from differing fields
We need the ability for the report to pull the estimate from a feature AND if there are multiple time estmates on the requirements tab , the aggregate of that time needs to overwrite the time range on the overview tab on the feature
Capacity planning - Do not allocate capacity in the past but only in the future
Who would benefit? Any User of the Capacity Planning report What impact would it make? Make it very clear when a non-completed item (Initiative, Epic, Feature) needs to be reschedule in the future. Rescheduling it will probably surface a capacity ...
Sébastien Lievain
11 months ago
in Capacity planning
0
Future consideration
Ability to view and edit "people" without having to go to a capacity report
Currently the only way to edit "people" is to go to their team in the config, or via a capacity report. eg change their schedule. It would seem to make more sense to see this data in the users profile (with the correct permissions).
When creating or changing a team, there is an option to manually set the teams capacity instead of having it calculated from #people*schedule. However, the manually set capacity is not reflected in the capacity report. The only way around this is ...
Fredrik Örn
almost 3 years ago
in Capacity planning
0
Future consideration
We have different teams that work around the clock in the each release. I need to be able to track per release the capacity so I can visualize each team individually and as a whole.
Dear Aha Team, Problem: you can estimate hours/people in advanced estimate that are outside plan duration dates (these can be manual or inherited). It leads capacity plan to ignore these entries and present false data on capacity view. This is ext...
Tomasz S
almost 2 years ago
in Capacity planning
0
Future consideration
'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...
Max Robbins
12 months ago
in Capacity planning
0
Future consideration