I use the planning tree to manage how stories fall into iterations and iterations into releases. My iterations, in real life, have an order: iteration 1 is followed by iteration 2, etc.. However, I’m not quite sure how to model this in a MQL query.
I’d like to be able to query against cards and infer an ordering of those cards. For example, I’d like to be able to get a list of the cards that are not done, but are booked in elapsed iterations. So I’d like to do something like this:
table query: SELECT name, number, iteration WHERE Type = Story AND Status != Done and Status != Deleted and Iteration < ‘(Current Iteration)’
The trouble here is that the iteration cards have no implied order. The “Iteration < ‘Current Iteration’) does not generate an error, but also does not produce the expected results. I haven’t quite figured out what logic is being used for the less-than. I’d like to do something like this, where StartDate is a property on my Iteration card:
table query: SELECT name, number, iteration WHERE Type = Story AND Status != Done and Status != Deleted and Iteration.StartDate < ‘(Current Iteration).StartDate’
Is there a way to do something like this?