This way I have one place to look for ideas and one place to update and configure the portal. There's too much going on if I have an ideas portal for each product and too many places I need to go to update categories if I have one that touches all of them
It's currently possible to add multiple products to your ideas portal via Settings -> Account -> Configure idea portals. In doing so, you can have a single ideas portal across all products in your product line (for straightforward configuration and management). And you can promote larger ideas to initiatives that live at the product line level. Given the low number of votes on this older idea, we are unlikely to make this change in the near future.
I would like to have idea portals to also either:
Live on the product line level
or to be able to live without having to be assigned to a workspace.
The use case here is that I need a portal that I can use with leadership to ideate long-term strategic initiatives, that may at some point become a workspace of their own. I'd like this portal to live on highest product line level (company level), where we have also defined the business initiatives and goals.
On the surface it seems a bit silly that we are ideating initiatives "that need to go into Aha"... outside of Aha!
As Aha goes into larger enterprise organizations the ability to include the Product Line level as an option to submit ideas to is important for us. We deal with many internal and external stakeholders(sales, customer experience, end-customers, partners) that would like to submit an idea that might not be specific to a product but go across the product or is more relevant to the product line.
+1, I don't believe the capability being described actually exists in Aha, even though this says "already exists".
I would like the ability to add an Idea to a Product Line, which is different from adding an Idea to a Product within a Product Line. Early in an Idea's lifecycle, it may be premature to decide exactly which Product should implement the Feature that solves for the user need expressed in the Idea, and may only be able to possible triage it to a higher level Product Line bucket. A portfolio owner for a Product Line should consider whether to solve for the Idea in existing Product A, existing Product B, or create a net-new Product C within their portfolio to address the Idea.
Also, the behavior is different in the two modes. For a single product portal, you get the "all" list of the product and its optional categories. When you have a product-line portal, you actually don't get that top-level "all" category that you get with a single-product portal - you only get the products within the product line.
That may be, but it's still product-specific categories. what we want is a product-line hierarchy, so you can submit ideas to a "general" bucket at the product line level, or target a specific product.
It's frustrating that for a single-product portal, it works as expected and you can add custom categories. But with a product line portal, you lose that higher level of hierarchy and ability to capture general ideas.