RELATED IDEAS
Moving an idea between workspaces should not remove it from the portal
Sometimes, an idea is submitted to a portal that is mapped to a different workspace than the one that needs to respond. When moving the idea to the correct workspace, the link to the original submission is no longer valid and the submitting user effectively looses their ability too see the submission
3
MERGED
Continue to track ideas in private portal when they are moved to a different workspace
What is the challenge? When idea moved to relevant team workspace, submitter can no longer track idea status in private portal What is the impact? Submitters get no feedback and can't tell if their idea has been picked up and is being worked on or...
0
Future consideration
1
MERGED
Unbreakable Aha Links Between Workspaces
What is the challenge? Roadmap Owners lose visibility to Ahas they have submitted on behalf of the business because the Aha links break when they move from one intake workspace to a specific team workspace. What is the impact? Customer confusion D...
0
Future consideration
1
MERGED
Change of Functionality to idea portal
We have a central intake idea form/intake portal for all of Consumer Product. We love that and it works great. The hiccup... Because ideas are coming in so fast and furious, we are moving the idea from the CP main intake portal to the journey itse...
0
Future consideration
1
MERGED
When moving ideas to different portals notify the users
What is the challenge?
When an idea is moved between portals or workspaces the user who created the idea does not get any notification. Although the Idea ID doesn't change the user will not be able to access the idea under the old portal and mus...
0
Future consideration
1
MERGED
When a customer logs an Idea under the wrong workspace and we move it the to appropriate workspace it nolonger is visible for others to vote on.
What is the challenge?
When we move an Idea to another workspace it is not visible in the idea portal
What is the impact?
Customers have no ability to upvote the idea so we lose all ability to understand if it is important to others.
D...
0
Future consideration
© 2026 Aha! Labs Inc.•All rights reserved
This is very important for us as well. Initially we may not know the specific product / workspace when the ideas are submitted. We need the ability to move the idea to the correct product / workspace after triaging the request without the original submitter losing access to it.
This is critical for us. Customers don't always know the correct workspace, they take a guess in order to submit their idea. We need the ability to move the idea to the correct workspace/PM without the customer losing access to it. The way the system is currently working, we can never move ideas to the correct workspace, making idea management and reporting difficult.
This is also a problem when an idea is moved from a current product to a product being developed and not yet released or moved to a component of the product. In both cases the workspace the idea is moved to is not listed on an external portal. In both cases using a category to track them is not sufficient. A customer needs the ability to track and monitor their ideas no matter where they are moved. You have submit-only portals, maybe you need a read-only portal where the original link a customer has is still valid and they can track the status of their ideas even when moved to a non-external portal workspace.
This would also have to incorporate another idea that is listed which talks about suppressing the workspace name. This is important for pre-release products where we do not want competitors to know about our future plans.