View Issue Details

IDProjectCategoryView StatusLast Update
0008149mantisbtfilterspublic2019-07-26 04:49
Reporterjotango Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status acknowledgedResolutionopen 
Summary0008149: New filter option: [Someone] for Assigned to and other filter fields
Description

Often I would like to filter for issues which are assigned to someone (i.e. the reverse of none).

I would propose adding the filter option [Someone] to the "Assigned to" drop down lists in the filter section.

The [Someone] option should only include issues who are assigned to someone.

Additional Information

This should not be just for the user fields it should cover other fields where a 'Not Empty' query is needed.

TagsNo tags attached.

Relationships

has duplicate 0008266 closed filter on not empty field 
has duplicate 0005370 closedthraxisp Add additional standard filter attributes ('not empty') 
has duplicate 0007408 closed filters should be used with a "has a value" possibility 

Activities

whobe

whobe

2008-08-05 21:49

reporter   ~0019047

Last edited: 2008-08-05 21:49

I'd like to say that this isn't exactly the same as my original suggestion too.
I'd suggest instead of "someone" use "set" or "not none" because someone implies it refers to a field which represents a person and I'd like to use this feature in other fields as well. I'd like it to be in all fields that currently have none as an option so I can filter on resolution and the like.

I propose something different which would seem to be all together more useful. That is an option to invert the meaning of any selection. That could mean If I choose "suspended" from the resolution and then check the "invert" or "not" checkbox next to the resolution, the meaning would be equivalent to requesting all tasks whose resolution is not "suspended"

This would work for assigned to to none as well. Just check "not" next to assigned to, select "none" from the dropdown and this would select all tasks which are assigned to someone.

I'd suggest having a checkbox next to each filter option for this purpose. It would leave the existing code essentially untouched and simply complement the select statement for that field.

atrol

atrol

2014-01-25 09:37

developer   ~0039176

Unassigned after having been assigned for a long time without progress.

stevecharon

stevecharon

2019-07-26 04:49

reporter   ~0062428

Although this is still something I want to have, you could achieve this by using advanced filters in 2.x Version and Multi-Select all possible Values
and there you have your "not empty" filter.
Dont get me wrong. This is just a workaround! If you have a long list of values it really sucks this way. A single [notempty] is way better IMHO.
Workaround works in 2.5.2 and 2.21.1 (dont have other versions running).

Issue History

Date Modified Username Field Change
2007-07-13 08:13 jotango New Issue
2008-08-05 21:19 daryn Relationship added has duplicate 0008266
2008-08-05 21:21 daryn Assigned To => daryn
2008-08-05 21:21 daryn Status new => acknowledged
2008-08-05 21:21 daryn Additional Information Updated
2008-08-05 21:49 whobe Note Added: 0019047
2008-08-05 21:49 whobe Note Edited: 0019047
2008-08-05 22:11 daryn Relationship added has duplicate 0005370
2008-08-07 11:20 daryn Relationship added has duplicate 0007408
2014-01-25 09:37 atrol Note Added: 0039176
2014-01-25 09:37 atrol Assigned To daryn =>
2015-10-30 05:18 kminnu Issue cloned: 0020234
2019-07-26 04:49 stevecharon Note Added: 0062428