Hello Peter,
it's really good that someone asks these kind of questions because all of us benefit.
How's the life cycle of an issue which gets fixed ?
Issue has been submitted
Status is unconfirmed
Issue has been confirmed and/or has been sent to a developer
Status changes to new
If the developer accepts the issue then he/she sets the state to started
If the issue has been fixed then it's set to fixed
As issues are usually fixed within child workspaces this means that the issue has been fixed on its child workspace
Then the developer sends the issue to someone within QA
If the issue has been verified then the issue is set to verified (verified on the CWS)
Before an issue which has been fixed within a childworkspace can be integrated all other issues within this CWS need to be verified as well and (automated) regression testing needs to be done before the QA owner of that CWS is allowed to set the CWS to "Approved by QA"
Then this CWS gets into the queue of approved CWSes which need source code review before they get approval (nomination) to get integrated
Additionally some child workspaces get separate attention by the "CWS gatekeeper". This is someone who checks the workflow of some randomly selected CWS. If he finds problems then the CWS owner needs to fix these problems.
If the fixed issue gets integrated into a master workspace then the QA owner of this issue verifies it again and then closes the issue
Now the issue is fixed.
Kind regards, Joost
Sorry to look stupid, but that would imply/explain the difference between Resolved:Fixed & Resolved:Closed.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
