Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
Quick Filters allow you (or anyone else using this board) to further filter the collection of issues appearing in Work mode or Plan mode. By default, a board contains two Quick Filters, called 'Only My Issues' and 'Recently Updated':
デフォルトのクイックフィルター | デフォルトの JQL | 注意 |
---|---|---|
自分の課題のみ | assignee = currentUser() | 現在このボードが表示されている人に割り当てられた課題を表示します。 |
最近更新された課題 | updatedDate >= -1d | 24 時間以内に更新された課題を表示します。 |
必要に応じて、追加のクイックフィルターを作成できます。以下の例を参照してください。
Any additional Quick Filters that you create they will appear as buttons next to the 'Only My Issues' and 'Recently Updated' buttons on the board (see Using a Board).
ボードのクイックフィルターを編集する手順は、次のとおりです:
次の表と スクリーンショット 1 (下記) に示すようにクイックフィルターを編集します。
編集項目 | 操作方法 |
---|---|
新規クイックフィルターを追加する | 青色エリアで、「名前」、「 JQL 」およびオプションの「説明」を入力し、「追加 」ボタンをクリックします。新規のクイックフィルターは、クイックフィルターの一番上に追加されます。 |
クイックフィルターの名前を変更する | スイムラインの「名前」エリアをクリックして、既存の名前を変更し、「更新」ボタンを押します。 |
クイックフィルターの JQL を変更する | スイムラインの「 JQL 」エリアをクリックして、既存の JQL を変更し、「更新」ボタンをクリックします。(提案については、以下の例を参照してください。) |
クイックフィルターを削除する | スイムレーンの右側にある「削除」ボタンをクリックします。 |
クイックフィルターを移動する | Hover over the vertical 'grid' icon, then drag and drop the Quick Filter up or down to its new position.
|
For JQL syntax, see the JIRA JQL documentation.
スクリーンショット 1 :「ボードの設定」画面 - 「クイックフィルター」タブ
クイックフィルターを設定する JQL の使用例:
" バグ修正 " グループのメンバーに割り当てられている課題をすべて表示する場合
assignee in membersOf("bugfix")
種類が「バグ」である課題すべてを表示する場合
type = "Bug"
クイックフィルターで JIRA フィルターを使用する場合
savedfilter = "My Filter"
For more details, see the JQL documentation.
33 Comments
Armin Schubert
May 08, 2012Hello
let us assume we have some quick filters set up.
The are link via AND which means if i click two quickfilters, only the ones valid for both criteria are displayed.
Is there any way to switch that to a link via OR which would display all tasks which match at least one of both criteria?
Thanks in Advance
armin
Robert Sundin
Dec 20, 2012+1
As a workaround I sometimes use “inverted arguments” to get the OR function.
In its simplest form it could look like this: [filter1 : issutype!=bug] [filter2: issuetype!=change]
It´s a bit counterintuitive for the user since [filter on] becomes [filter off] and for some combinations of filters the JQL gets a bit messy…
Roger Henty
Apr 15, 2013+1
We'd like this too, we have to make a huge number of quick filters because we can't combine them. Even supporting the "~" for more fields (like assignee) in advanced JQL searches seems like it would resolve this issue.
Has anyone found a workaround? I don't think we're going to be able to use inverted arguments, unfortunately.
Thanks!
Georgi Mitov
Jun 04, 2013+ 1 for having the option of combining quick filters with OR.
Rosie Jameson [Atlassian]
Jun 07, 2013You may like to watch/vote/comment on GHS-8975 - Getting issue details... STATUS
Anonymous
Jun 12, 2012It would also be nice to have the quick filters in a configurable drop down menu instead of all next to each other.
Anonymous
Jul 04, 2012Why, when I create a custom Quick Filter, (i.e. fixVersion = "version name") and filter by this in the "Plan" portion of the Rapid Board, and then subsequently drag and drop an issue from the filtered view into the sprint - does the sprint then get populated with ALL issues that were above this one when I remove the filter.
This behavior is not evident for the two pre-existing Quick Filters, and don't understand why this would happen with a customized filter.
We've just started the process of switching over to JIRA/Greenhopper from Rally - if we can't get basic filtering in a Backlog with hundreds or thousands of items, it doesn't seem like the Atlassian offering is of any use to an Agile developing team. I've tried Atlassian answers, and emailing the support team directly and have not received any response - I would appreciate an answer to this.
Anonymous
Sept 27, 2012From my point of view extending quick filters with a few simple changes would add hugely to the usability of these boards-
e.g. allowing things like
assignee = <VALUE>
but allowing <VALUE> to be selected from a dropdown in the quick filter
This would mean I don't need to create a separate quick filter for each team member (which only works because only a small part of the team is using this)
Anonymous
Nov 08, 2012Agreed, scrum master needs a way to easily filter board by user for daily stand up.
Anonymous
Dec 27, 2012Yes please! The lack of this feature (filtering a board by user) may well keep me from using this version of Greenhopper. Much as I feel like a grump for reverting to "Classic" view....
Anonymous
Oct 25, 2012Is there anyway to make these act like radio buttons? I constantly get Smart people who do not realize that they are seeing not results because they have applied mutually exclusive filters.
Thanks.
-Gary
Anonymous
Nov 26, 2012+1 on OR, very irritating...
Anonymous
Feb 14, 2013+1 on OR
Anonymous
Nov 26, 2012+1 for assignee = <VALUE>
other example - fixVersion = <VALUE> should allow me to drop down and choose that on the board.
Anonymous
Dec 06, 2012Is there any way to export/import the quick filters? This would be useful as we setup quite a few for a board.
Rosie Jameson [Atlassian]
Dec 10, 2012Not as such; one possibility is to copy the board – the new copy will have the same Quick Filters as the original board.
You may like to watch/vote/comment on GHS-6397 - Getting issue details... STATUS
Anonymous
Feb 16, 2013This is good but could we change this Quick Filter on the borad itself instead of click on config.... Too many clicks
Anonymous
Dec 10, 2012+1 for an alternate OR-switch
Anonymous
Dec 11, 2012+1 for assignee = <VALUE>. This is a feature we used quite often using the classic task board.
Rosie Jameson [Atlassian]
Dec 16, 2012You should be able to do this already? (Please see the documentation on Advanced Searching#Assignee)
Apologies if I'm misunderstanding your requirement.
Anonymous
Dec 27, 2012Hi Rosie -
I think what we're looking for is an easy way to filter by any user who currently has tasks - similar to the assignee filter in the Classic planning board. It's too much work to create individual quick filters for each user on a project who might have a task assigned. I'd like a filter: Assignee [ dropdown with each user's name ]
Thanks!
- Caroline
Rosie Jameson [Atlassian]
Dec 30, 2012Hi Caroline,
You may want to try using Assignee-based swimlanes? (please see Configuring Swimlanes)
You may also like to watch/vote/comment on GHS-5389 - Getting issue details... STATUS
Hope this helps,
Rosie
Anonymous
Dec 18, 2012How about filtering for unassigned tasks?
Anonymous
Dec 18, 2012assignee is EMPTY
edwardkfrancis
Jan 08, 2013Need the ability to have a quick filter that shows stories assigned to the currentUser(), but all tasks within the story.
Anonymous
Feb 05, 2013With reference to Armin's comment in May 2012, we are also encountering the same problem with quick filters.
We have one Agile board with multiple projects assigned to it, I have created several filters
Filter A - project = 'a'
Filter B - project = 'b' etc
When you select only one of the filters the projects issues are filtered as expected, however when you then select a second filter as well you are presented with error Issues may be hidden by Quick Filters.
I believe this is down to the concatenation of filters using the AND operand.
Has anybody found a workaround to this problem?
Thanks in advance
Robert Sundin
Feb 05, 2013I use inverted functions. It´s not perfect but it works for me.
Filter A – project != ‘a’
Filter B – project != ‘b’
It´s a bit counterintuitive as clicking “filter on” means “filter off”, but you could set the name of the filters to “Hide A”, “Hide B” etc to state it´s actual function.
Anonymous
Feb 06, 2013Hi Robert
Thanks for your prompt reply! I had already tried this as per your original post but this doesn’t quite give us what we need.
In total we have 10 products and a number of people or responsible for 1, 2 or 3 or those products using the method you’ve described I would need to create lots of different filters to hide the different combinations of products, which would have you’ve suggested be a work around but might not be easy for our product specialists to work with when they are working with the backlog.
Any other ideas would be appreciated.
Thanks in advance
Robert Sundin
Feb 06, 2013Hi,
I would really like the requested feature too, but I haven’t seen a really good workaround so far.
Just one comment about the number of filters required though:
I don’t think that you need any more filters using this workaround then if the functions were concatenated thru an OR statement. You need one filter per project in each case (if I understand you correctly) but the users need to think “backwards” in the workaround.
Besides this, I´m out of ideas and hope for someone to come up with a better workaround
Chris M
Apr 11, 2013Is it possible to copy quick filters from one board to another? I guess the other option is to copy the whole board...
Rosie Jameson [Atlassian]
Apr 12, 2013No, and yes that is definitely an option.
laurence bascle
May 03, 2013Ensure you vote for the feature here GHS-4534 - Getting issue details... STATUS
Ronny Hanssen
May 29, 2013The two examples shown above work nicely together.
But, the case I am looking for is to have one quick-filter per developer which could be combined (like the two samples). This would make it easy for me to turn on and off issues and show only issues for those selected. I tried to create something like this:
"assignee = JohnDoe"
"assignee = MaryPoppin"
But, that didn't work. I had small hopes, but also tried to use "assignee in (JohnDoe)", which of course also failed. That is - they work on their own, but the filters cannot be applied at the same time. I guess that the JQLs are ANDed and the case I try to make needs an OR
...
I wanted to use this during our daily sprints, but there may be some other handy way of doing them? I recall http://sprint.ly/ having some nifty features for easily showing a summary of activities since last daily standup. Anyone know a solution that I could use for this in JIRA/Greenhopper?