Add support for quick filters in a similar way to GH's rapid board
This suggestion has been implemented in Structure 3.4! Check out release notes: https://wiki.almworks.com/x/AYvrAQ
Aggelos Paraskevopoulos commented
Thank you very much for the efforts, and the fantastic product you are building with such a great passion.
All the best!
Not released yet, but already working on it!
So is this released/available yet?
That definitely helps! Thanks Igor!
We're releasing Structure 3.0 within a few months (beta version is going out in a few weeks). Then we'll be working on major improvements, and this is one of them. We still haven't planned after-3.0 iterations, but I can tell you that Quick Filters were actively discussed during Structure 3.0 implementation and we even considered including that feature in 3.0. It has been pushed back because of timing constraints, however, the groundwork has been laid, and we'll definitely get to it soon after 3.0 release.
Since the earliest time for version 3.1 will be 1.5 months after 3.0, and the earliest time for 3.0 is in 2 months, I can currently tell that this feature will not be delivered within the next 3.5 months, but very likely soon after.
Hope this helps!
My company is considering purchasing Structure and this feature is the primary reason we would consider passing. We basically need to be able to filter our Structures by assignees and components so that we can focus on the right tickets at the right time. I know in your last message you said you were interested in doing it, but it wouldn't be for the next 6 months. Do you have any updates on timing?
I've created a feature request - https://jira.almworks.com/browse/HJ-2071 - feel free to vote / watch it! It's an interesting feature and we'd like to get to it anyway after 3.0, but at this time I cannot promise specific dates. I do not expect this feature to appear within next 6 months though.
exactly - you got it!
I tried to use JIRA (and add plugins) to get a quick overview about stories, epics, issues etc. no (easy, straight forward) way. It's really weird that there no way to have this kind of view at glance.
And having this in Structure would be a perfect usability feature - and as I mentioned, at first step sufficient for components and labels.
When do you plan to release Structure 3.0 - anything we can do to have this Autofilter feature in 3.01 ...?
Thanks for your input. This is a great idea, thanks. I see it basically to what Excel provides with "Auto-filter" feature, where each columns gets a drop-down where you can select the values for the filter.
We'd like to add that to Structure but I doubt we'll be able to do that in Structure 3.0; hopefully in a later version!
I just worked for 3h with GH / JIRA Agile, JIRA Portfolio and Structure.
I like the Structure Plugin the most - but there is one serious issue (especially with GH / Agile): it's quite complex to filter the list based on multiple criteria.
- GH: only one epic and version per entry
- GH: no display of labels and components in the plan mode, only if you display the issue details
If would be perfect to be able to filter based on accumulative criteria: labels and components.
These are the most important and most common use elements in JIRA used to structure the content.
I know, we could reach the same with quickfilters, but this would be a very very time consuming job to create a quick filter for each component and label - nightmare.
- As a structure user I can click on labels (on = include, off = exclude) and the list of issues in structure will be filtered automatically
- As a structure user I can click on components (on = include, off = exclude) and the list of issues in structure will be filtered automatically
Of course a list of available labels and components, either for all or for specific projects. To reduce the complexity, as first step it would be sufficient to select the projects which will be used to extract labels and components as klickable filter.
Community / ALM Works - what to do think?
Ben, thanks for your suggestion!
Ben De Pauw commented
Agile board filters are defined on the board definition, while filtering is possible when using/consulting the structure.
In that sense, it would be helpful to simply place a 'save' button next to the filter box & allow the user to store the filter type + filter value text as a quick filter (e.g. mutex push button list as quick-select on all saved filters).
The saved filters could be stored alongwith the views (columns, size & sequence), which would allow to share with other users
Or should we say Agile's Rapid board ;)
Maxim Merkushev commented
Yes it is the same. Thanks
Maxim, thanks - is this the same as http://structure.uservoice.com/suggestions/2710409 ?
Duncan, thanks for your comment! We will work on it for sure, but please bear with us, as it's not making it to version 2.0. I've put this feature on the tentative list for 2.1, but no promises.
Whether it's a small task depends on what task you compare it to :) It is certainly not trivial, and it will take considerable effort to do the right way. (And we won't do it other way.)
Seems like a small task compared with many of the others in the feature requests list, for a large benefit. We use filters a lot to drill down to specific sub-backlogs in our structure views, and typing the JQL queries every time is quite cumbersome. It's also not the easiest thing for non-technical users to do. Please do implement this!
Hi Aggelos - thanks for the idea! Certainly worth doing.