View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008149||mantisbt||filters||public||2007-07-13 08:13||2020-05-25 13:59|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Summary||0008149: New filter option: [Someone] for Assigned to and other filter fields|
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.
This should not be just for the user fields it should cover other fields where a 'Not Empty' query is needed.
|Tags||No tags attached.|
|related to||0004864||new||Unable to filter on empty custom field value|
|related to||0012798||new||Add a filter option [Something] as opposite of [None] i.e. field not null|
|has duplicate||0008266||closed||filter on not empty field|
|has duplicate||0005370||closed||thraxisp||Add additional standard filter attributes ('not empty')|
|has duplicate||0007408||closed||filters should be used with a "has a value" possibility|
I'd like to say that this isn't exactly the same as my original suggestion too.
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.
Unassigned after having been assigned for a long time without progress.
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
I've proposed a pull request on github : https://github.com/mantisbt/mantisbt/pull/1670
|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|
|2020-05-19 09:09||l2m||Note Added: 0064003|
|2020-05-19 14:27||dregad||Relationship added||related to 0004864|
|2020-05-19 14:27||dregad||Relationship added||related to 0012798|