[#JRA-2681] Extend filter capablities by adding negative clauses

JIRA

Extend filter capablities by adding negative clauses

Created: 15/Nov/03 07:23 AM Updated: 20/Jun/07 08:58 AM

Component/s:

Filtering & Indexing

Affects Version/s:

2.6 Pro

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

JRA-1560 Better support for logical operation (and/or/not) type of filters.

This issue is duplicated by:

~~JRA-4009~~ I want to see the issues reported by me but not assigned to me

Reference

This issue relates to:

JRA-9115 Ability to search for issues with no due date associated

JRA-1560 Better support for logical operation (and/or/not) type of filters.

JRA-6180 Search for a custom field that is empty

JRA-1635 "not" qualifier on fields for searching

~~JRA-699~~ Filter on multiple projects

This issue is related to:

JRA-9073 Negative user / group filter

Participants:	Daniel Dyer, Dmitry Kashin, Geoffrey Wiseman, John M. Black, Judith Bürgstein, Martin Read, Nick Duncan, Owen Fellows, Pearl, Shelby, Peter Žagar and Werner Schulz
Since last comment:	57 weeks ago
Labels:

Description

« Hide

It will be useful for finding Issues reported by all developers excluding one specified and others.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Owen Fellows - 16/Nov/03 07:58 PM

Improved search functionality

[ Permlink | « Hide ]

Peter Žagar - 07/Jul/04 06:01 AM

Usefull when I want to see all isues reported by me(current user) but not assigned to me(current user) or assigned to all but me(current user)

[ Permlink | « Hide ]

Nick Duncan - 27/Sep/04 07:03 PM

I would love to be able to find all the issues that are not closed, for example.

[ Permlink | « Hide ]

Pearl, Shelby - 13/Sep/05 09:21 AM

I agree, this would be very useful. For example, I could create "Affects Version" or "Fix Version" filters that exclude all of the version numbers that don't apply to the release-under-test, which means I wouldn't have to update my filters every time a new "Unreleased" internal build was deployed for testing. (We operate in an environment where major releases overlap so there is more than one set of release numbers in the "Unreleased Versions" section).

[ Permlink | « Hide ]

Martin Read - 24/Jan/06 05:13 AM

In our instance, I would find it very useful to search for all issues that are overdue (relative) OR where no due date is set.

[ Permlink | « Hide ]

Judith Bürgstein - 05/Apr/06 06:30 AM

I'd like to have exactly the same filter Peter Zagar mentioned: reported to me but assigned to someone else.

[ Permlink | « Hide ]

Geoffrey Wiseman - 17/Apr/06 10:22 AM

I've just now had a good use for 'assigned to anyone not in <group>', and there's no good way to express that.

[ Permlink | « Hide ]

Daniel Dyer - 09/Aug/06 10:46 AM

I would welcome the feature described by Geoffrey above. All of our project developers belong to one group. We would like to be able to filter issues assigned to people outside of that group so that we can see where our external dependencies are.

[ Permlink | « Hide ]

Werner Schulz - 16/Jan/07 07:23 AM

Agree with Martin Read's earlier comment to able to find issues without a Due Date.

[ Permlink | « Hide ]

John M. Black - 27/Feb/07 04:30 PM

Agreed that a "Not" concept per-field would solve most or all of this. The use case I'm thinking of is "all versions except Future". We use a version called "future" as an easy bucket for indefinitely-postponed issues. (We thought this was simpler than using a separate status for Postponed.)

[ Permlink | « Hide ]

John M. Black - 28/Feb/07 11:36 AM

Please vote for JIRA-1560; that seems to be where all the votes are being pooled for this.

[ Permlink | « Hide ]

John M. Black - 20/Jun/07 08:58 AM

Please make sure you've voted for JRA-1560; we are trying to get a groundswell of support.