Investigate adding query support

[dmranck]

Investigate adding support for querying tickets in a project based on certain parameters. For example, return all open tickets, or return all tickets assigned to a specific user.

[dmranck]

Not sure how to generalize this across all 5 tools. Slightly outside the scope of CRUD as well.

[dmranck]

More notes:

It'd be a nice feature to have, but it's a hard thing to generalize across 5 tools. And I do like how the current implementation of ticketutil contains methods that are very consistent across the tools, hiding the differences and complexities of the APIs from the user and giving them one consistent way to interact with the tools.

I also feel this is slightly outside the core scope of ticketutil, which is a Create, Read, Update, Delete tool. Even within these 4 main operations, there's a lot of work to be done.

If there's a strong justification for adding this feature, I would just want to make sure it's done as consistently as possible. While I would prefer the search(**kwargs) route [1], I don't think this is practical with all the different query fields, groupings, comparison operators, etc. If we went the "jql" route [2], we'd just need to clearly document this for each tool, which does put some complexity back in the hands of the user, unfortunately...

[1] We could possibly do something general like search(**kwargs) and each module would know how to translate those kwargs into specific valid query but that way we might lose a lot of searching abilities e.g. how to specify AND, OR between specific parts of the query, grouping of parts of the query etc.
[2] The user would have to know how exactly to formulate the query based on which ticketing system they're using e.g. jql for jira

[dmranck]

My initial high level view of how this would work would be a function that accepts a jql query string or something similar in bugzilla and then returns the list of tickets returned from that query.