Hi Chris referring to the implementation, I experience that the prefix will be specific to the sub product the ideas portal is configured to. Meaning when someone adds an idea on sub product A but the portal is configured under product B the prefix is misleading. Or do I miss anything?
We now plan on adding this capability with a design that supports all of the benefits described by Jonathan Heron.
The configuration of idea portals will move from the Product Settings to the Account Settings section. This will allow a single portal to span multiple products. If you configure you portal with multiple products then users will be prompted to choose the product before creating a new idea.
Some benefits of an Idea Portal for a product line:
You could build the nested categories list in the portal sidebar based on Products › Categories › Subcategories, so ideas are automatically filed under the appropriate product. By filing ideas under products in this way…
Notifications can be routed to different PMs as ideas are added.
Searching within the full database of ideas by product becomes much easier.
Moving an idea to a product doesn't cause it to disappear from the portal.
Hi Chris referring to the implementation, I experience that the prefix will be specific to the sub product the ideas portal is configured to. Meaning when someone adds an idea on sub product A but the portal is configured under product B the prefix is misleading. Or do I miss anything?
We now plan on adding this capability with a design that supports all of the benefits described by Jonathan Heron.
The configuration of idea portals will move from the Product Settings to the Account Settings section. This will allow a single portal to span multiple products. If you configure you portal with multiple products then users will be prompted to choose the product before creating a new idea.
Some benefits of an Idea Portal for a product line: