'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
10 months ago
in Capacity planning
0
Future consideration
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
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...
Valentina Morales
10 months ago
in Capacity planning
4
Future consideration
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
over 2 years ago
in Capacity planning
0
Future consideration
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
over 1 year ago
in Capacity planning
0
Future consideration
Initial estimates -option to change the default to support parallel planning
Currently the initial estimate defaults to the number of days between the start and end date of an EPIC (and feature). At the EPIC level this can through off our capacity planning if the advance estimates are not updated when the EPIC is created. ...
Ruth Gardiner
11 months 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.