Coalesce common dependencies in the dependency map
Right now, I have a task which depends on several other tasks, and some ofthose depend on the same underlying tasks. An example of this would looklike:
A / | \B | C \ | / D
I would expect the dependency map view to draw a line between B&D as ...
Many times we come up with ideas that is related to multiple product like .com and mobile. It would be awesome if we could associate one feature and /or idea to multiple products using cloning.
Guest
over 10 years ago
in Features
1
Unlikely to implement
Allow Reviewers to Change Status and View History on Features and Master Features
Our workflow starts with product management creating a roadmap of features and master features in Aha. Engineering responds by changing the status to "understood", "committed", "will not fit", etc. Seeing the history on that provides a record of w...
Julia Doyle
about 6 years ago
in Features
0
Unlikely to implement
Link features to other features and if you choose "duplicates" as the link then they should update each other in real time
Link features to other features and if you choose "duplicates" as the link then they should update each other in real time to have them remain duplicates. Ex. if one feature is shipped, we want the other linked feature's status updated as well to ...
Guest
over 8 years ago
in Features
2
Unlikely to implement
Ability to show each initiative as a card on Feature Board view with hierarchy of features cards
When treating Epics as Initiatives and Stories as Features, I'd like to use the Feature Board view (like this view because you can see individual feature cards by release and drag/drop between releases). Currently, this view only shows cards for F...
Brandon Fleisher
over 8 years ago
in Features
1
Unlikely to implement
Master Features and Features should be more interchangeable.
Aha wants to replicate the concept of epics as master features and features as stories. However, they treat them as separate entities which makes really hard to report a list of ‘features’ together (including master feature). For instance, JIRA ca...
Guest
over 7 years ago
in Features
0
Unlikely to implement
Some of our features end up with a large number of related items in the record links section, and the card view of the feature ends up looking very cluttered. It would be great to be able to fully collapse the record links section, and in that vie...
Guest
over 7 years ago
in Features
0
Unlikely to implement
Ability to enter 'time logged' quicker and easier across multiple features, releases, products etc
Hi
As we are moving more towards Aha time tracking facility, would it be possible to have a quicker/simpler way to enter time. Currently the team log time in 1 hour increments and with upto 8-10 hours a day, this can be upto 8-10 feature cards tha...
Guest
about 9 years ago
in Features
0
Unlikely to implement
Shared custom field options between Features and Ideas
We have a custom editable tag field on both Ideas and Features. It's great that the Idea field values come over automatically when the Idea is promoted to a Feature. It would be even better if the list of available tags automatically synced betwee...
Chris Humphreys
over 8 years ago
in Features
1
Unlikely to implement
Update status of requirements on status change of feature
I don't want to change the status of each and every requirement individually when changing the status of a feature. For example, when I hand off a feature - which has 5 requirements, for example - to engineering to spike, they come back with a ful...
Guest
over 9 years ago
in Features
4
Unlikely to implement