Bumped. In particular I need a 'Confirm fix' status. So the developer checks in a fix, marks it 'Confirm', then another developer (or tester) confirms the fix works and marks the bug Resolved. TFS has this but they call it Active/Resolved/Closed.
Bumped also for the general ability to add states.
I was going to file specifically for just the addition of "Verified" - representing the state that follows testing ... in my experience "Resolved" indicates that the developer has tried to fixed an issue but the probability of it being actually resolved is far less than 100% the first time around. So the Resolved state (or whatever dev marks a bug after applying a fix attempt) is best viewed as a queue of work for the testers. The output of testing needs a state.
The tracker is really unusable process wise until there is some reasonable capability here. Since my team started a project on bitbucket, we're giving it a go, and I'm using a milestone (verified fixed) and assignment to "nobody" as a temporary solve.
Another +1 from me...
Even just adding "Testing Needed" would be very nice!
But if possible custom workflow would be very nice (similar to the components field where you can add your own workflow status...
I could use this, as well. Right now we've re-purposed the "wontfix" status to indicate verified/certified (once QA has tested the change). I kind of feel that "wontfix" and "invalid" have somewhat overlapping meanings anyway.
We joking say, "we won't have to fix that again"... but a more explicit status for this would be nice.
At this time we do not have an estimate for when this feature will be implemented. Our focus for the short to medium term, will be to provide SSO and better user management with our OnDemand JIRA and Confluence products. I would estimate that the SSO integration and bi-directional oAuth integration between Bitbucket / JIRA / Confluence / Bamboo will take us well into 2014, at which time we will re-evaluate this decision.