We are just starting to use the ideas portal - we have officially rolled it out to all of our salespeople.
Right now we can link ideas to features, but we would also like to be able to create relationships between ideas.
Why is it useful?
Who would benefit?
Product Managers responsible for reviewing, following up, and implementing the ideas would benefit from this idea.
How would it work?
The Action menu for an idea would include 'Link idea to another idea'.
Options for relationships would be the same as for features - relates to, depends on, duplicates, contains, impacts, blocks, and their opposite relationships (is a dependency of, etc.)
This is possible today. From the Actions menu on any idea, you can link the Idea to another record (which includes any idea, initiative, release, release phase or feature).
You can read more about it here: http://blog.aha.io/universal-dependencies/
This feature would be very useful to me, as many of the ideas being submitted have dependencies: in order for idea C to be implemented, we must implement ideas A and B first. I am currently using a custom field to list these dependencies, but it's clumsy. While this is certainly not a "must-have" feature for me, it would make managing the ideas portal much easier.
I can see the benefit of creating a relationship between related ideas that are not duplicates.
With regard to duplicate management, we already have the "Merge" capability for merging duplicated ideas together. The benefit of merge is that it also integrates subscribers and votes into the main idea.
Adding watchers - Jeet Patel and Per Risberg