Ponder Q23 History

Query tasks with a custom boolen field set to false

Event Timeline

Higgs asked this question.Nov 3 2022, 18:36

Higgs created this object in space S1 Public.

Herald added subscribers: Cigaryno, Matthew. · View Herald TranscriptNov 3 2022, 18:36

valerio.bozzolan added an answer.Mar 9 2023, 06:15

How do you currently express your search query?

Feel free to share more details even if it's closed - we can alway reopen. Thank you

valerio.bozzolan closed this question as invalid.Mar 16 2023, 15:55

Its basically a predefined query that is called via conduit:

(echo '{"queryKey": "xxxxxxxxxxxx"}' | /opt/phabricator/arcanist/bin/arc call-conduit --conduit-uri https://our.phorge.service/ --conduit-token our--conduit-token -- maniphest.search) > resultfile.json

The basic problem is that boolean queries only allow for "true" or "ANY" but not for "false" and i never understood for what reason that is.

Can you share a screenshot to this fact of... true or any but not false? Thank you so much

(Please set that file as visible to everyone)

Screenshot:

Definition of the custom field that is queried:

"our.customfield": {
    "name": "Supportfall",
    "type": "bool",
    "search": true
  }

Higgs attached a referenced file: F269265: phorge_boolean.png. (Show Details)Mar 16 2023, 17:45

valerio.bozzolan updated the question details. (Show Details)Mar 16 2023, 17:58

Since the answer of this is "sadly this is not possible now" I elevated this as a Task:

T15177: Allow to query Tasks with a custom boolean field set to false

Thank you. Marking as Closed.

valerio.bozzolan closed this question as resolved.Mar 21 2023, 07:59

@Higgs It seems to me, that it really does not filter by true, but it filter by "It has this field set to true, or false". That is why the filter is called "Require". Can you confirm this guess?

No, the filter only fires when the value is set to true. When the value is not set or set to false, the filter does not fire. I believe that for boolean fields there is no way to distinguish ‚false‘ from ‚not defined‘ which might be the root cause of the issue.
Furthermore when i define the field as required, then the only accepted value for the field is ‚true‘ which makes no sense at all to me.