Hide results in the initiative selector to only show those within the workspace Merged

What is the challenge?

As an Aha! user / product manager, I want to more easily find the best initiative to attach to my release or feature without scrolling through endless initiatives in other people's workspace that have no relevance to mine, so that I can save time connecting records.

What is the impact?

This will save a product manager several minutes each time they go to connect an initiative or goal to a releases or feature since they won't be encumbered with hundreds of initiatives and goals (that are relevant to the portfolio but not to them). It will also improve accuracy greatly of attached the right initiative or goal to the release/feature, given often they select one that sounds similar but is in a different area of the portfolio. This leads to a lot of cleanup by the Aha! admin and product manager down the road.

Describe your idea

The solution to the problem is to make visible only the initiatives or goals for a given workspace when an Aha! user first pulls up the selector, while hiding all the others, unless the Aha! user clicks "show more". We have tried the workaround of using timeframes against initiatives and goals and then archiving the timeframes, but we need initiatives and goals active for 1 year (we do strategic planning each fiscal year), and we have up to 10 active initiatives per product area with 10 product areas in our portfolio - meaning 100 initiatives active at any given time (probably 50 goals in total). This makes it impossible to comb through every time a product manager is working with the initiative or goal selector, since they are looking through 100 items, many of which may sound close to the one they created in their workspace. Additionally, it would be nice to partition product lines from each other within these selectors as well. That would reduce the set to choose from significantly when the portfolio is large and consists of multiple product lines.

Other workaround solutions:

1 - Another solution that would help but not fully resolve it would be to allow "Achieved" initiatives to at least be hidden from the drawer.

2 - A Timeframe "stamp" at the end of each initiative or goal would give a user more context and perhaps a hint that an older initiative may no longer apply. Often, the task of sunsetting older timeframes may accrue for up to a year, given we have no dedicated product ops function. And, often product managers have similar sounding annual initiatives, because we try to break up very large initiatives that span multiple years into more manageable delivery chunks at the annual level or several quarter level.