In the feature list, there is a filter option called "Score not entered." It would be useful to us to have a similar one for estimate (i.e., Estimate not entered), so that we know which features need an estimate from engineering before proceeding to the next step.
Has ANYONE come up with a creative solution to this problem. How are you working with capacity planning (using this field) when it is so lacking in versatility (ie sorting and filtering) At the very very least being able to know if something is NULL would be super desirable.
We have no way to find features that do not have an estimate. This is very important for scoping and budgeting a project.
This is a critical item as part of our processes. Please include in a future release.
I would ask the question "Why are ANY fields excluded from filtering?"
All fields should be available for sorting and filtering (estimates are also not sortable, which is disappointing to say the least).
yes, need this to be able to quickly view what hasn't been done.
Super important - need to focus my team on estimating items, and being able to quickly find the features in upcoming releases that arent even estimated is crucial to driving the conversation.
Similar to the comment above -- I'm currently syncing estimates into both the actual Aha supported fields, and some custom fields so I can do things like compare actuals to estimates, find unestimated items, etc.
I'm surprised this is still not supported, I used to have a custom "Effort" field until I realised that Aha! has the idea of effort estimate built-in. So I delete all my "Effort" field values, moved them over, only to find I lose this kind of functionality now.
Is there any plan to introduce this?
I was looking to create a pivot report with Master Features/Features without estimates vs with estimates.
I would extend this to Requirements, which can also be estimated.