Fixed Not Tested Follow
I've introduced Charisma and now YouTrack as our bug tracking system here at work, and I'm trying to put together a simple guide for the developers and testers here.
I've used several other bug tracking systems before and it is usual for the developer to mark an issue, once they believe it is fixed, to something like "Fixed, Not Tested" and assign a version number for the fix.
The testers then, once they receive the new version of the release, filter issues that are marked as "Fixed, Not Tested" for this new release, to ensure that the issues really are fixed. If they are, they would then set the issue to "Fixed". If it was not, they would set it to something like "Not Fixed".
Now, in the case where a YouTrack issue was tested and deemed not fixed, we could set the issue to "Open".
However, I'm stuggling to work out which state to use as "Fixed, Not Tested" with out it feeling like a hack.
Is there a way for me to add this state to the system?
Am I missing something?
Please sign in to leave a comment.
First, there's no "Fixed, not tested" state in YouTrack 1.0, and you can't modify predefined states.
Turns out we've introduced the "Verified" state in EAP build 67 :-)
That'll do nicely thanks!