Currently, users can only select one tag and one category. It would be very helpful for users to be able to add multiple tags and categories.
We have reopened this idea and will consider adding it to our future roadmap.
Until then, you may want to add a custom tag field to your idea form. Portal users can select multiple tags when they submit an idea.
Also, as an Aha! user you can edit an idea within Aha! to assign it to multiple categories.
We have a master category of "Cameras" and would like all child categories (camera manufacturers) to also apply the master category of "Cameras" as well as the manufacturer that the user selects. Right now, it requires manual moderation to add the category/s once the user has submitted an idea, which is not ideal.
We want Ideas Portal users to be able to select multiple Categories. Internal Users are able to do this but Ideas Portal users (customers) cannot.
We would like to use the Ideas categories field as a'Single' selected category. But when administering/reviewing ideas within Aha, the Categories field is a multi-select tags field, whereas within the portal view it is not. This is Inconsistency and bad.
So if Aha wants to provide this multi select tag option, they should also continue to allow 'categories' as a single selected predefined list and remove the discrepancy of the multiple select on the backend tool.
We were recommended by Aha to map our products to category as the best way to filter by product on the main portal page. We want our customers to be able to browse through each product and find more ideas that relate to them and vote/comment/engage, etc. However, we were very surprised to find that it did not work as expected because of this gap.
For example, we have reports that apply to multiple products, and so we need to multi-select the product (and need the field Category to be a multi-select field on the idea portal form). This is a big hindrance to adoption- please reconsider to implement.
Has there been any consideration on improving this feature since the last comment in 2018?
It's a big gap in being able to reasonably organize incoming Ideas - I'm evaluating Aha for my organization right now and this lack of feature is leading us to review other solutions.
Right now, I can only see how to add a Category from the Admin Ideas console inside Aha and cannot retroactively add a Category if a public user posted an idea from our Ideas Portal.
Beyond multiple categories, the lack of retroactive Admin ability to tag Categories makes it difficult to organize Ideas for a larger organization.
Tags are somewhat helpful but not the same, and normally a Tag would function as a Sub-Category.
Agreed with Marie on this one.
Understanding you could do it using tags, but this isn't consistent. We can assign categories in the admin portal but users cannot assign multiple when submitting a new idea. The experience should be consistent.
At the very least, give us the ability to choose when setting up the portal. Allow us to choose for people to either select from a drop down list (as it is today) or allow for multiple (as we are suggesting here).
I agree with Marie, Suzie and guests' comments on the issue. I just started using Aha and I have the same impediment. I would appreciate the possibility to add multiple categories in the Ideas Portal, same as is possible within the Aha
I agree with Marie's comment -- we would certainly make use of multiple categories per Idea if the option was available. Adding tags for categories is redundant and prohibits users from filtering.
As Richard noted, we can add multiple categories from within Aha. My users want to be able to add multiple categories from the start. Also, since users can filter by categories in the portal, I want them to be able to find their ideas under all the relevant categories. If I use tags in addition to categories so I can have multiple, not only am I duplicating work but my users can't then filter by the tags.
Yes, but then we end up with redundant category fields. Further, when administering/reviewing ideas within Aha, the Categories field is a multi-select tags field, whereas within the portal view it is not. Inconsistency = bad...
;-)
I agree that the portal should also support multiple categories.