Once an issue is in status 'resolved' it can not be commented on or otherwise revised. That is detrimental to the process because many of the 'resolved' staff comments state something like "should be ok, please check".
(example:
<<Comments
✓ Posted by Nayru at Thu, 19 May 2016 11:25:08 UTC
Should no longer occur. Please verify.>>

If, as on several occasions, the issue is not resolved or not resolved completely, one needs to open up a new issue, get confirmations again, votes again etc. that just adds time and confusion to the process. For example the 'Theurg ice pet moving forward between casts' issue was claimed resolved in 0545, but was still occuring, so a new issue(s) had to be opened and the problem is still not fixed (at least till yesterday).

So staff, it would be great if you could either:
add an intermediate issue state, something like "resolved pending confirmation', or
allow the 'resolved' state to be commented on and changed back to confirmed/assigned

cheers

Yes agreed, the ticket should be assigned back to the owner for verification. If verified the ticket would get closed. If not it would be assigned back to the dev in charge of it

Create a feature request for it!

How am i suupose to post a screenshot of an item for bug reporting now using google drive?

Lotendan wrote:Yes agreed, the ticket should be assigned back to the owner for verification. If verified the ticket would get closed. If not it would be assigned back to the dev in charge of it

That wouldn't work for a lot of tickets. Commenting on resolved issues is a problem as long as there are no notifications, since the comment would simply get lost. (Who looks at resolved issues?)

I think right now the best way would be to create a new issue and link to the old issue if there's still a problem. (This is what my "please verify" comment was about. If ok, just do nothing. If broken, file report.)

thanks for explaining Nayru

cheers