It seems that the BSA adds the "regression" key word automatically if there is a "Latest known-working version" selected before the "Version".
This often is correct, but sometimes, of course, the bug is related to a new feature; for this kind of bugs I believe it's common sense that we do not set the "regression" Keyword.
Although the number of bugs with inappropriate "regression" might be not too big, the problem is annoying because this keyword means some kind of alarm for many of us. So I wold prefer a solutions that adds a text to the comment as a reminder for QA staff ("Possibly regression?").
I recommend to wait for some comments and then to decide whether we leave this BSA feature as it is or do a modification?
Operating System: Windows 7
Last worked in: 220.127.116.11 release
Adding Rob, who was updating the assistant during the Hackfest, and might have more insight
Already solved after hearing from it via the ESC-notes of thursday.
sorry was to soon with my reply. This isn't solved.
Now the regression-version needs to be older then the version. That's been changed this week. But what you describe isn't.
But it could be a good improvement, and easy to implement.
Thanks for the nice fix there Rob - lets see what the impact on regression keywords is now. We could add a label like "Not sure" instead of "None" in that dialog, to try to make it more socially acceptable to people to state that they actually don't know whether it is a regression or not.
Can we do tool-tips over widgets ? a tag saying "only fill this in if you have verified that it worked in a previous version" might be helpful.
Anyhow - thanks again :-)
(In reply to comment #4)
> Thanks for the nice fix there Rob - lets see what the impact on regression
> keywords is now. We could add a label like "Not sure" instead of "None" in
> that dialog, to try to make it more socially acceptable to people to state
> that they actually don't know whether it is a regression or not.
None is for me something different then Not sure. But I want to change this anyway. I just need to see how I can do that. I want a check-box if the bug is a regression and when the check-box is enabled then I want to show the select-box.
> Can we do tool-tips over widgets ? a tag saying "only fill this in if you
> have verified that it worked in a previous version" might be helpful.
Due to the change I want I don't think this would be necessary then.
> Anyhow - thanks again :-)
Any news on this? Does it still needs to be changed?
Tested: the described behavior applies. If version with bug is newer than last worked version, keyword "regression" is added. Rainer describes the edge case that this might be a new bug instead of a regression.
@Rob: I find your suggestion of a checkbox most useful. Any chance to add that? Adding that would allow us to not have the keyword added automatically and producing false positives.
Setting to NEW.
If you think this is bogus, please state your opinion.
not related to a product version.
This is now solved by using PossibleRegression and not Regression anymore.
Is this a good solution?
Not sure. It’s much better than the current state. A checkbox might be better because it requires active user participation and without that it won’t be set. But then again, not all users are familiar with the triaging process and keywords involved.
Rob, I guess let’s set this to revolved fixed and open a new bug if dev or qa are not satisfied with this solution. We’ll go from there then.
It is about using regression keyword, not a regression itself -> regression keyword removed.
Best regards. JBF