Create Operation Information - Continuous Improvement Ticket

[patrickisaac]

Description of the Tech Debt

After clicking Save Operation Representative, the fields were blanked out – should this be the behavior? It is not very apparent that the Operation Representative was actually saved.

Page 13 of this document created by @fviduya shows the necessary steps to reproduce

Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level	Value
High	3
Medium	2
Low	1

Technical Debt - Risk Types	Level	Value
Business Area Risk - Risk of business area visibility / damage to user experience	0	0
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it	0	0
System Fault Risk - Risk of system errors or application downtime	0	0
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?	0	0
Time Sink Risk - How much will this tech debt slow the development process down	0	0
TOTAL SCORE:	0	0

Development Checklist:

• Checklist item
• Checklist item
• Checklist item