Copy idea from one product to another.

I would also like to see the ability to Copy an idea to a new product workspace without first creating a duplicate within the original workspace. We use a central idea repository for customer feedback, since the feedback we receive often applies to multiple products (as suggested in the Aha! knowledge base: https://www.aha.io/support/roadmaps/strategic-roadmaps/ideas/create-central-workspace-to-manage-ideas.) When an idea in the central repository gets reviewed we create corresponding ideas in one or more product workspaces and relate them to the original submission. At this point in the workflow we are uncertain whether we want to proceed with a feature and therefore do not want to promote the idea.

We want to add the idea to the one or more product workspaces and relate it to the original. As the original submitter commented, creating the duplicate in the original space makes tracking by Reference IDs confusing and the process more error-prone.

I also think the current idea Copy action is problematic because it creates the copy in the background and the only visual indicator that it has been done is a prepended [Copy] in the idea name. (I've also become somewhat blind to the [Copy] text since it apears so often. I sometimes create multiple copies "[Copy] [Copy] Name" by accident because of this.) All the other idea actions (Promote, Merge, Link) prompt you with dialogs. A dialog that allows me to link the copy to the original, tweek the name and select a different workspace before it saves would improve my workflow significantly. If I like the default, it would only add an "Enter" keystroke to the current workflow and make it behave more like other actions. In eather case it would be more obvious that a copy has been made.

In light of my prior comment, please consider reopening this request or providing another alternative.

Thank you for the quick response. The problem with this solution is that our various products have different numbering schemas. When you change the product, it doesn't change the idea reference to utilize a) the numbering schema for the new product, and b) the next number available for the new product. This causes confusion for anyone tracking the issue through the process. Please reconsider implementing this request!