It seems like a common scenario would be to use the results of an existing query and add conditions to that.  So, instead of starting with a condition, I start with a shared query, then add conditions.

So, why would this be a good thing?  Lets say I want a group of queries dealing with serviceability work items.  The first report may be all serviceability items which may have several conditions to locate them.  Now I want to create other reports that are subsets of the report.  For example, all unresolved.  Ideally I would somehow indicate start with my serviceability query (not re-enter all the conditions) and just add the condition for status unresolved.

This is not just being lazy by not having to code up the serviceability query each time...  The criteria or conditions that determine serviceability items may change.  If I have to duplicate that code in every serviceability report variation, I will have to update every query that is based on those conditions.

So, is there a way to define a query that starts with the name of an existing query or invokes an existing query?