id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
1913,0.11 workflow compatibility,bewst,bobbysmith007,In the reports I see conditions like\r\n{{{\r\n   t.status IN ($NEW_ $ASSIGNED_ $REOPENED_ $CLOSED)\r\n}}}\r\nbut for 0.11 all reports with \r\n{{{\r\n    status IN ('new'_ 'assigned'_ 'reopened'_ 'closed )\r\n}}}\r\ngot upgraded to\r\n{{{\r\n    status <> 'closed'\r\n}}}\r\n\r\nIf you don't make a corresponding change_ tickets disappear from reports when their status becomes {{{'accepted'}}}_ and presumably the new workflow means tickets can go through any number of other states.  I think this fact leads naturally to reconsidering the appropriateness of the status checkboxes in the query UI. ,defect,closed,high,TimingAndEstimationPlugin,critical,fixed,,aqualx@gmail.com,0.11