Features

For example, We may have our engineering team (or QA team) in Aha! as "reviewers" and we would like them to participate in escalating status - such as: Engineer would say "In Development" when they start, and "Development Complete" when done. Then...

We have Master Features with the same names in multiple releases, so when we are connecting a Master Feature to a Feature, there are duplicates in the list of Master Feature but we cannot tell which Master Feature is with which release to connect ...

Please could you give us a description field on the time logging form? At this moment we cannot describe what kind of work the amount of time was for. We can only enter the amount of time. We need more insight in the kind of work that has been don...

I can have Master Releases that span Products, but I can't review the collection of features against a single budget. This is in our case a software package that is integral to a hardware product release, and is also available as a Product in its ...

In creating the metric inputs you can add the units and a prefix eg. £ But when you create a Scorecard itself (which I do to work out number of Resource (Slider) * Days (Slider) * Cost (Fixed per Resource) the output is in £/$ but the scorecard is...

As we evolve towards a continuous workflow, the concept of the Release becomes redundant. Yes, there should be a difference between Deployment and Release, but we still want to Release at the Feature level, if possible. So requiring Features to be...

It would be great if we could add multiple initiatives to a feature card

Ability to edit Dependency types within the link. Currently, user needs to delete dependency and create new one. For example, as a user, if I label a dependency "Depends on" and the dependency type should be "relates to", I should be able to chang...

When editing or viewing a feature for example then selecting the release "tab" a completely different release appears. Meaning you have to find and select the correct one each time. Selections should maintain the context across tabs as you usually...

When mapping the Progress field via an integration, the field should be enhanced to say something different when it is mapped e.g. “Mapped via Integration” or even better “Mapped from Rally” instead of "Enter manually". Also, the user should not b...