RELATED IDEAS
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 reflect.
This would benefit companies with numerous businesses and ones that have many co-developments.
-
ADMIN RESPONSENov 10, 2016
Thank you for the request. The "duplicate" selection is meant to be used more as a way to indicate that it may be a duplicate item of an existing feature (and may no longer be valid).
By drawing the links, it allows you to see how items are linked. In regards to businesses with co-developments, making use of the wide dependencies feature can allow you to see the connections.
At this time, we do not have plans for automation in this area based on current priorities. We hope you can understand.
5
MERGED
Enforcing Status Changes based on Dependency Links
Sometimes we have a feature that needs to be displayed in two or more different roadmaps. However, we don't want to have to make status changes to each one separately. The duplicate dependency link should work such that the whole feature card is d...
0
Unlikely to implement
5
MERGED
Duplicate with status mirroring (duplicate not clone)
I need to show the same feature in a number of releases. The only way to do this in Aha (confirmed with support) is to create a new feature in each release and link them as duplicates. The problem is that the duplicate feature is just a hyperlink....
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved
I need to show the same feature in a number of different workplaces. The only way to do this in Aha is to create a new feature in each workplace and link them as duplicates. The problem is that the duplicate feature is just a hyperlink. I need status and tags to be linked so that when the primary record is updated this updates all features marked as duplicate. Without this Aha is created manual work for us to manually keep them updated (risk of error) We are a big company with multiple divisions - with different workplaces. One division could have the feature in their workspace as needed, but is being delivered/developed by a different division. This is common in big companies.
Either you implement this or have a button below linking called "Share feature" which creates a duplicate copy that would allow updates to flow bidirectionally from one feature to the other.