Tag Separation by Product

Yes please! We only want to see our workspace's tags. It's a mess seeing 1000 other workspaces.

Even if tags can't easily be defined by product it would be really helpful if when you were on a report/view and you filter by tags it only shows the tags that are applicable for that report/view.

Needed especially for growing product portfolios and bigger product management teams - every product is a little different, every product manager has a different day-to-day routing to organize his roadmap and release plans in Aha! The flexibility of tags is great for that, but the more they are used the more cluttered the list becomes and, in turn, the usability suffers. Same actually for other dropdown selections, like releases.

With the three merged ideas, this feature is well articulated and is needed. Administration of Aha! would be simplified/easier to support Product and Portfolio Managers.  More important, the alignment/ precision in creating and using tags amongst many participants is focused.

We currently have several product management teams all using their own tags. But we also need to share some tags across the teams for certain shared standards (portfolio reporting especially).

At this point, the read-ahead only shows tags starting with "a" or "b" because 9 product teams all have their own tags. But we also need some shared tags (across products) as well, to support certain standards.

This feature is needed to ensure continued adoption of the tool among 4 different product teams and many more products. 

We need this, super beneficial to us!

Agree 100% + 10

We need this as well. Please make this enhancement!

agree a 100% ... we are a large aha client, have multiple products that we manage (literally 100'tes) and it gets really cumbersome with all of the tags across all of the products. In an ideal case, I would like to have the option to share tags for certain fields across the aha! deployment OR just for a certain product.

Very much need this, as we would like to have idea portals for multiple products and then be able to manage the ideas that both portal users and internal operation are using. Product managers on one product are less like to use tags or use them well when they are always seen in filtering and other situations at the account level. This creates a lot of noise and is a disincentive to use for multiple products in an enterprise and is influencing organization's decision to commit to this product beyond our department.

We are experiencing the same issues.

Any ETA?

We need this. Too many redundant tags floating around. Ideal to have tags that can be filtered by product / release.

ETA?

There is a need for this however I would say it also needs to be balanced with the ability to optionally see the tags that are used throughout our Aha! deployment.

We need this. The number of tags in our system has become overwhelming due to the needs of 8 different product groups.