Filter by Ideas Portal Name

I have a single product but multiple ideas portals. I use these portals for internal product suggestions and externally by different clients or stages of the client, e.g. a POC or beta test might get a new portal created for just a short term use. I also have a portal dedicated to capturing bugs from end users. All of this stuff gets mixed together on the Ideas List and filtering by email domain is insufficient. (Bugs btw will never be promoted to features or epics in Aha but instead will be captured in JIRA, if reproducible by the team.) Anyhow, it seems pretty obvious to want to be able to filter/categorize and create different views within Aha that correspond to the different ideas portals outside of Aha. I contacted Support and they said it was not possible at this time.

  • Guest
  • Sep 5 2017
  • Unlikely to implement
Release time frame
  • Sep 16, 2017

    Admin Response

    Thank you for the idea. Currently, ideas are related to a specific product even if they are submitted from different portals. In the use case that you mention here the suggested solution would be to leverage idea categories or tags. 

    At this time given the solution mentioned above and current priorities, we do not have plans to address the specific area noted. We hope you can understand.

  • Attach files
  • Christian Stark commented
    April 25, 2018 16:22

    I hope you reconsider this decision since your assumptions seems wrong. I basically need to be able to create a list (report) showing ideas coming from a specific portal. It makes no sense that in your UI that field isn't available. 

    We have multiple division leveraging various idea portals and it is essential for us to differentiate between the portals the ideas came from. We expect to manage hundreds of ideas coming in per week.

    Also I don't understand how categories help solve this since you can't auto assign a category based on the portal the idea came from.



  • Laura Giles commented
    05 Mar 22:53

    Much like lead generation, 'source' is very important, especially when we are working to consolidation all our feedback channels into one repository. There are different SLAs associated and needs for different portal users, closed betas/ETFs, etc.

  • Laura Giles commented
    05 Mar 22:54

    There's no reason why a unique identifier field can't be filtered on if it's even permitted to be displayed in the view.