Label range filter is not working properly

[gsmalter]

I frequently inspect code by using the History feature, and I filter by both label range and user. Basically, I want to see everything touched by a certain user from the previous inspection's label to the current inspection's label. Lately, about 50% I do this, I end up re-inspecting the same code because something is not working properly. Initially I thought it was because I was applying a label without refreshing first, but I've been really good about that and it's definitely not causing the problem.

I've attached a screen shot that clearly illustrates files whose date is before the date of the first label in the range. Notice how the first label in the range is dated 2/9 at 1:20PM. But files modified at 11:11AM on that day are shown in the list.

I don't remember ever having a problem with this before version 5.

[Beth]

Do you label only current code, or do you sometimes label from history?

I ran a test where I labeled some areas of history, and those labels will have a date of 2/12/10 because that's when the label was applied, even though I was labeling files as far back as 2008. Then I ran a history query between two labels. Due to where those labels were placed, the history range I received went from 4/15/2088 to 8/22/2008, but the dates on the labels are still 2/12/2010.

[gsmalter]

I always label by right clicking a folder in the tree of the main Vault window.

[Beth]

Is it possible that those files are part of the first label? View the first label and check some of the files and dates of those files that are part of the label.

[gsmalter]

I don't understand. Of course the files are part of the first label. They are also part of the second label. Every file is part of every label - I am labeling $. There are also thousands of files that are part of both the first and second labels that (correctly) aren't showing up in the list, because no changes were made to these files in between the time the first and second labels were created.

[Beth]

I meant the versions, but that's ok. We're going to run a few tests here to see if we can recreate the issue.

[gsmalter]

I can tell you that the files are are incorrectly showing up were part of the previous inspection. So, they were changed at some point (maybe even the same day, as in this example) before first of the two labels but after the previous (let's called it label zero) label.

So, if the labels I showed you in my example are labels 1 and 2, the files (more specifically, the same versions of the same files) I showed you are showing up in the range label 0 - label 1 AND in the range label 1 - label 2. I hope that helps.

[Beth]

We've recreated the issue and have a bug logged. Thank you for reporting this.

F: 15254