RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit AFPR-I-7567 Reference capacity planning fields in calculated column equations.
Allow Master Feature original estimate to be used by calculated columns
Merged
I'm creating a List report but the "Master feature original estimate" column cannot be used as a calculated column.
I sync custom data back to Aha! from Azure Dev Ops so want to see the difference between the "Master feature original estimate" and the data in my custom field.
© 2024 Aha! Labs Inc.•All rights reserved
I am also interested in this. I am creating some reports and syncing; trying to workaround the default conversion of the original estimate field into minutes. It's more natural for our team to think in hours or days. Things are fine in AHA. They can choose whatever unit they want; 10h for 10 hours, as an example. This becomes 600 in Devops if synced to the effort field there. We're not tracking granular task management, so this level of granularity with the time estimate is distracting.
I know there is another idea to enable configuration of this. I would be happy if I could include the Original Estimate field in calculations fields on list reports for both Features and Master Features.
Do you have a timeframe for this?