...
Proposed changes will be submitted to the CCB with an explanation of the need, changes and consequences. These can be recorded in blogs (aka "news item", labeled sassoccb) in any space, if desired. Otherwise the content can appear entirely in jira itself. Approval will be recorded here also. Consideration and approval may be done via email, evo meeting or phone depending on the urgency of the request. We will start off by requiring unanimous approval from the board members for the action to be approved.
...
- requestor creates a Jira item in the SSC project, leaving the state as "In Preparation". If you have created a news item to track the content of the request, fill the url into the CCB news item url in the Jira issue.
- once it is ready to go, the requestor selects Submit to SAS-SO CCB from the workflow. This puts it in the hands of the CCB.
- the CCB determines the "severity" of the request (whether to send to the LAT &/or and Mission CCBs) and changes the priority on the issue.
- Then the issue is routed to the approriate next CCB or approved (or rejected)
- if a minor issue, and approved then the LAT CCB is notified of the change
- if approved, the issue is assigned back to the requestor, who sets the issue to "Implemented", and then closes the issue or the CCB folks do.
...