It's all about the answers!

Ask a question

Artifact Filtering on "Exists" Returns Results - Along with Blanks


David Reilly (697) | asked Feb 06 '18, 11:50 a.m.
edited Feb 06 '18, 12:50 p.m.

We have been using the filtering system in DOORS Next Generation v6.0.2 iFix005 for quite a bit now. I'd like to consider myself to be rather good. 


I've grown fond of selecting "exists" as that seems to suggest that data is populated. My question is such, if I create a view for a string attribute that I would like to update, and specify one of the following dropdown options: 
  1. Contains
  2. Does Not Contain
  3. Is
  4. Starts With
  5. Ends With
  6. Exists
  7. Does Not Exist
  8. Is Unassigned
When reviewing the CSV file exported from the system, I found that the number of artifacts with my attribute populated are 5700 out of 23,000. I think we overshot this one quite a bit. 

How do you define "existence" other than "is not blank?" Furthermore, any advice on which of the above options I should be using to get the results we want? 

Thanks,
David

One answer



permanent link
Carol Watson (6216) | answered Feb 06 '18, 12:34 p.m.

 I've noticed the same thing so am also interested in the answer on this one!  


Thanks,
Carol

Your answer


Register or to post your answer.