Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Is This An Expected Behaviour? Trains Version 0.16.4, Not Able To Upgrade Now To Latest Version But I Doubt This Was Changed

Is this an expected behaviour? trains version 0.16.4, not able to upgrade now to latest version but I doubt this was changed

  
  
Posted 3 years ago
Votes Newest

Answers 13


New version will contain much more advanced search (including all the task fields)

are there any more fields in this function with partial matching? for example project? tags?

Yes they can all be filtered (basically everything you see in the UI)
notice: tags are strings (you can provide list of tags), project is an ID of the project
(Use Task.get_project_id, I think)

  
  
Posted 3 years ago

Problem is obviously the names won't match

  
  
Posted 3 years ago

I expected an exact match for the name

  
  
Posted 3 years ago

Ohhh I see, yes this is regexp matching, if you want the exact match:
'^{}$'.format(name)

  
  
Posted 3 years ago

That's the whole query

  
  
Posted 3 years ago

or they behave, as expected, via exact matching

  
  
Posted 3 years ago

AgitatedDove14 , are there any more fields in this function with partial matching? for example project? tags?

  
  
Posted 3 years ago

Also, could there be an "and" logic implemented in the task_filter argument for Task.get_tasks? currently it only supports "or" logic

  
  
Posted 3 years ago

Hi SmoothArcticwolf58 ,
The tags field is a list of strings and does not support the regex query 🙂

  
  
Posted 3 years ago

It seems treating this like a regex solved the issue. Again, I am not sure why partial matching is the default behavior.
And again, please oh lord, please, allow for and logic in this function. This would ease up computations a bunch (I filter on multiple tags and doing it one tag by one currently)

  
  
Posted 3 years ago

No, I meant, are the tags behaving in this regex manner as well?

  
  
Posted 3 years ago

More advanced search is great, but please try to include "and" behavior between multiple options as well (for example, "and" logic on multiple tags)

  
  
Posted 3 years ago

SmoothArcticwolf58 could you copy paste the entire query and what is the expected results vs reality ?

  
  
Posted 3 years ago
1K Views
13 Answers
3 years ago
one year ago
Tags