Allow simple computed fields in query output

[jbates-2]

I would like to be able to create simple computed fields in a query definition where the computed field value is based on fields in the returned items. For example, in a query that lists items with an Actual and Estimate field, I would like to be able to compute an Accuracy field, per item returned, based on those values from the query definition itself.

From a UI or API perspective, these computed fields would need to somehow be differentiated from real fields to reduce the number of occurrences of users trying to find that field for reporting.

[mrump]

Do you mean something like a "inline report"?

[jbates-2]

An "inline report" may be overkill, but would certainly be an interesting idea. I think if I were to need all of the reporting capability, I would use a report and push users in that direction instead. I was thinking about being able to solve the following scenario in a query only, which could then be used behind a QBR or as input into other reporting capabilityes (report, chart):

I have a list of User Story items that contain Defects found during testing. I would like a query to return the User Story items, but include a count of open defects as one of the fields. Ideally, I would like to be able to subquery or aggregate, or aggregatebytree to find all of the downstream defects, and then filter those by Phase (Defect Phase = "Open"), and return a count. A computed field in a report or chart can do this, but not a query, and therefore not a QBR.