Reviewer users should be able to change a feature's (or requirement's) up to a certain point
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...
Guest
almost 11 years ago
in Features
3
Will not implement
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...
Guest
over 5 years ago
in Features
1
Future consideration
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 ...
Guest
over 5 years ago
in Features
1
Future consideration
Add Units and Suffix/Prefix to a Scorecard (Aha! Score)
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...
Paul Mundy
over 8 years ago
in Features
0
Unlikely to implement
Enable the ability to move the Feature draw details
I would like to be able to move the "Feature" draw details to somewhere on the screen that is more comfortable when updating the feature from on the board. I find it being locked is awkward. I sit facing forward and my keyboard is in from, yet the...
Guest
almost 3 years ago
in Features
0
Future consideration
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...
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...
Max Cascone
over 8 years ago
in Features
0
Unlikely to implement
We will be using Approvals as gates for requirement rejection and/or deferrals. The approvals team will need arguments and data to make the evaluation. With the current functionality the Approval is sent as the Feature enters the relevant state an...
Guest
almost 3 years ago
in Features
0
Future consideration
Progress field to visibly show when its mapped in an integration
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...