|the issue has just been found, and hasn't been analysed yet, or there is new data about an existing issue.
|Waiting for Feedback
|the report was insufficient to analyse the issue, and more feedback is needed from the person named in the "Waiting For" field. Once the reporter has added feedback they should flip the state back to "New". If feedback is not received within 30 days, the issue will be discarded.
|the issue has been analysed, and the priority has been confirmed (or changed) by a developer. The item can henceforth be classified regarding release blocking status etc. Someone needs to pick it up and fix it.
|Being Worked On
|the issue has been analysed, and is being worked on by the developer named inthe "Waiting For" field.
|Waiting for Release
|the issue reported has been fixed and is queued for release. See the TargetRelease field to see whether it is queued for the next patch, minor, or major release. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why.
|the issue has been fixed to the satisfaction of the fixer, and has been through the "Waiting for release" state, and is now released to end users. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why. Note that bugs reported against new code (code that has not been released yet) or Extensions (Plugins etc) may jump straight to "Closed" without going through "Waiting for Release" first.
|No Action Required
|the issue was already fixed, or it's a duplicate, or a RTFM, or could not be reproduced and feedback was never received.