pending_ops_dev_analysis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
pending_ops_dev_analysis [2022/07/22 16:00] 10.91.129.11pending_ops_dev_analysis [2022/08/17 15:08] (current) 10.91.110.100
Line 1: Line 1:
- [[https://errigal.atlassian.net/jira/software/c/projects/OPSDEV/boards/91|OpsDev Jira Board]] +See [[opsdev|]]
- +
-[[https://docs.google.com/document/d/1AS1xf68axwSZS_juOZN8Xn_MpYkjGn4D/edit#|Ops Dev Process Doc ]] +
- +
--------------------------------------------------------------------------------------------- +
- +
-__**Ticket Management**__  +
-  +
- +
-**Development Required** +
- +
-A "Development Required" Label is required for any Ticket that: +
- +
- +
-  * Development ticket was raise instead of Ops ticket. +
-  * Is related to a Development ticket. +
-  * Had any Development involvement.  +
- +
-**Engineering Required** +
- +
-The Resolution Category of "Engineering Required" should be added for Tickets that have to be resolved by a Development release or a patch.  +
- +
-In both cases, an IDMS reference needs to be added to the ticket under the "Related Development Reference Tickets" field. +
- +
-This means the relevant ticket reports are correct some of which customers receive or may ask for. +
- +
-**Triage**  +
- +
-Tickets that will not have Operations involvement initially and will need a Development ticket will remain in Triage until the ticket is raised and the estimate confirmed.  +
- +
-If the ticket is a bug fix a ticket is raised, communicated to the customer and the Ops ticket is closed. +
-If this is a Development request then the Ops ticket will follow the approval process once the Development team have confirmed an estimate via the Ops Dev process. The Ops ticket will then close. +
pending_ops_dev_analysis.1658502041.txt.gz · Last modified: 2022/07/22 16:00 by 10.91.129.11