RELATED IDEAS
Filter Releases on Feature Board
I added a custom field to Releases for Project Type and created a filter for it on my Feature Board; however, when I select the Project Type I want to see on the Feature Board, it still shows all of the Releases for the product, regardless of Project Type, and only excludes the features for the release with the Project Type I've filtered out.
Because the Project Type is designated at the release level, I would expect only releases and features within the filter I have selected for the Feature Board to be visible.
I am aware that the current work around is to only select the releases I want to see from the release filter, but that means I need to have the Release Type (or any other Release field I want to filer the Feature Board on) memorized, which is not ideal.
-
ADMIN RESPONSEMay 30, 2018
Thank you for your idea. As noted, we recently added a "Release" filter to the features board which will allow you to select which releases to show on the board.
Given the ability to filter using the new releases filter, we are unlikely to add more release-specific filters at this time. We hope you can understand.
1
MERGED
Features Tab - Ability to remove Releases from Visual Display based on filter of Initiative
As an AHA User who works on multiple projects within the same product, it would be extremely useful if the initiative filter also removed the releases that do not pertain to the initiative selected so that i can see just the releases, parking lots...
0
Unlikely to implement
1
MERGED
© 2024 Aha! Labs Inc.•All rights reserved
Another echo here. It's a little bit head scratching why you can only filter using names. Seems like this should be an easy slam dunk to implement. The current implementation let's you add filters (other than name), but all they do is eliminate the features/epics associated with that release. It's kind of silly to now have the release still show up on the screen with no features/epics listed. Why not just hide the release as well?
Just adding a comment to echo that only being able to filter on names is unhelpful. As stated in the original comment, that requires teams to know explicitly what every release is called which is not feasible when teams can easily have multiple releases ongoing at any given time. It also presents an inconsistent UI/UX experience. If its not possible to actually filter out releases by other criteria, why allow me to create a filter which implies I can do that?
We need this P0 feature.
I agree, why place the ability to apply filters based on either custom fields that are part of both releases and features and then not have the releases disappear based on that filter. Seems counterproductive to say, oh, filter here and then yes filter all of these too, so my clicks turn from 2 to 10 to 20.
I was trying to do the same thing base on initiative association and it disappeared all the tickets but i had to manually select the desired releases and parking lots.
Definitely a hassle to have to do that every time.
This is painful for my team as well. We have internal/external releases and want to filter them for prioritization between different teams within this view.