Set BB issue status types according to stage in change procedure

USE CASE: WHAT DO YOU WANT TO DO?

Add information for developers when to set specific BB issue status types.

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

Open a bitbucket issue
Change the issue status

CURRENT BEHAVIOR

We have an implied procedure for setting issue statuses at this moment. It is currently limited to setting an issue as "Resolved" after implementing a change or to statuses like "WontFix" after discussion.

EXPECTED BEHAVIOR

BB issue status directly mirrors the meaning of the SCMP change procedure (SCMP_TreeView3.doc Section 3.2 - Configuration Control).

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

Add a (sub-)section that indicates appropriate status types for an issue depending on the progress through the established change procedure.

new: Submitted as change request, ready for review by CCB leader.
open: Reviewed and approved by CCB Leader - ready for implementation by assigned developer
on hold: Issue is not to be resolved for now, but might be in the future (various reasons)
duplicate: Issue actually duplicates another issue that has already been created (sometimes this only becomes clear after some time)
invalid: Disapproved by CCB leader
wontfix: Implementation of the issue cannot proceed (technical & architecture reasons only!)
closed: The issue has been fully implemented, reviewed, and tested and has been merged to production.

FILES AFFECTED (where the changes will be implemented) - developers only

SCMP_TreeView3.doc

LEVEL OF EFFORT - developers only

trivial

COMMENTS

Comments (8)