It's all about the answers!

Ask a question

Why are Unresolved and NOT Resolved statuses in queries returning different results?


Chris Newton (3035) | asked Jul 29 '14, 12:51 a.m.
  In RTC 4.0.1, we have some additional states for our defects, one of which is Deferred (assigned to the 'Open' OSLC group). I've created a work item query that grabs all unresolved work items in a project and it fails to return any defects in that Deferred state. If I change the query to "is not" + "Resolved", the deferred defects appear in the results. I couldn't find any other reports of this issue.

Is this a known bug?

There are some open defects that are similar, but not quite the same:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=165926
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=280129

Comments
1
Donald Nong commented Jul 29 '14, 11:29 p.m.

A quick test on RTC 4.0.4 shows that it works as expected.

Be the first one to answer this question!


Register or to post your answer.