1 / 2

SciOps Process

This protocol outlines the process for handling new functionality and bug tickets in ICT using Jira. Tickets are created by the SSS team for new functionalities only. Bug tickets are created as usual. Release impact is determined by ICT lead. Large work allocation is managed by SciOps/ICT Admin. Dates are communicated by ICT lead to SSS. If the issue affects more than one subsystem or requires significant effort, SciOps/CSCG is involved in planning.

elton-sheppard
Download Presentation

SciOps Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SciOps Process ICT Jira Ticket New functionality tickets only created by SSS. Bug Tickets Created as usual Y SCCB Affects deployed or fully planned release? Dates defined by ICT lead and passed to SSS N Y Affects more than one subsystem or “large” amount of work? SciOps / ICT Admin N Group Lead Planning

  2. SciOps CSV Process ICT Jira Ticket New functionality tickets only created by S. Corder Bug Tickets Created as usual Y SCCB Affects deployed or fully planned release? Dates defined by ICT lead and passed to SSS N CSCG

More Related