Fixed Not Tested

Hi Guys,

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?

Many thanks,



Hi Lee,

First, there's no "Fixed, not tested" state in YouTrack 1.0, and you can't modify predefined states.

We're planning to allow creating custom states and other attribute values in the next version.

However, you can use tags to enforce your scenario. Here's how it could be done:
    1. Developers act as usual, marking issues as fixed and assigning them version numbers. Sample command: fixed fix for 1.0.
    2. Testers search for issues resolved for a specific version. Sample search query: fix for: 1.0 #fixed.
    3. When a tester verifies that a particular issue was actually fixed, he/she tags it with a special tag, for example, "tested", using command add tag tested. If the tester reproduces the issue, he/she changes its state to "reopened" and (optionally) comments it.
    4. To get the list of issues to be verified for a particular version number, a tester uses the following search query: fix for: 1.0 #fixed -tested.

Whether to treat it as a hack or not, depends on personal preferences :-)


Turns out we've introduced the "Verified" state in EAP build 67 :-)



That'll do nicely thanks!



Please sign in to leave a comment.