Features

When pre-planning a release, I want to be able to move sets of features around under master features to ensure that there's enough capacity in a release to complete the full set of features under a master feature. To do this I want to rank all the...

The user will we able to import features/releases together with its record link dependencies. Especially with our way of using AHA, its very tedious for us to set record link dependencies one by one per feature/release. It would help us be more ef...

We use different feature and epic types and would like to have the option to color the cards on the features/board based on the type instead of the status for easier visual distinction of each card's type.

What is the challenge? The primary challenge we are facing is the presence of duplicate values in the lists generated by our custom field formula. We have a custom field in our feature layout that pulls values from a specific column in a related c...

Dear aha, I would like to propose showing all of the time tracking attributes on the features when tracking is turned on - Original estimate, Remaining work, Work done. Right now, with or without time tracking bar depending on new progress bar...

Currently the ranking in the Features Workflow board is not respecting the ranking from the Features Board. We use the workflow board for collaborating with the engineering team for planning and monitoring work. If we rank work in one board it is ...

Quick vier progress in features board.

What is the challenge? Currently, it is not possible to make the Product value scorecard or a custom scorecards read-only on the Prioritization view. What is the impact? This prevents you from being able to lock-in a scorecard because even if you ...

At the epic, or feature level you can find tabs with the following title "related, overview, comments, to-do's etc" which currently can't be renamed. Providing the opportunity to rename these tabs and use existing terminology that is already used ...

When a Requirement is shipped the remaining estimate will go to 0, but if that Requirement is re-opened then it will stay 0. Is there a way to restore the remaining estimate when a Requirement is re-opened?