Actionlist for fixed Issues

Common requirements

Check existence of Spec for Feature/Enhancements (see http://specs.openoffice.org)

Check if the target of the issue is set according to the target of the CWS

Identify possible risks

Identify possible dependencies with other OOo applications

Provide information to respective QA stake-holders
(e.g. file QA-child task respective dependency issue. Ideally add those to the respective CWS.)

Provide information at QA mailing list dev@qa.openoffice.org

If the issue is UI-relevant check correct adjustment of according flag for the CWS in EIS. Inform CWS-Owner if incorrect.

If the issue is Help-relevant check correct adjustment of according flag for the CWS in EIS. Inform CWS-Owner if incorrect.

Check existence of test cases in TCM - Test Case Management (Login to TCM)

Enhance old test cases if necessary

Create new test cases if necessary

Create task for appropriate auto-tester if necessary

Verify fix on (at least) two platforms

Verify issue against Spec and Feature mail

Run reasonable automated tests with VCL TestTool (at least run first.bas, topten.bas from framework/first)

Enroll test case/automated test

Contact developer

Inform QA-Representative and Owner of CWS

Reassign issue to developer, include a note into the issue and make sure the issue has been set to NEW

Add additional information about rejection in decription field for this CWS in EIS