Create IssuableSeverity model to store incident severity level
Problem to solve
An incident is a special type of issue. It needs to have additional information, for example, "severity".
To not extend the issues
table with the columns specific to incidents, we need to create a separate table to hold that information.
One solution would be to create the IncidentSeverity
model to hold information about the Incidents severity.
But most likely the list of Incident specific properties will grow. Having a separate IncidentData
should work better in the long run.
Based on the following discussion, create IssuableSeverity
model to store severity level of an incident.
Contributes to #229402 (closed) and #230980 (closed)
Intended users
User experience goal
Proposal
Create IssuableSeverity
model to store incident severity level.
Required fields:
issue_id
-
severity
integer allow NULL (for "unknown state")
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Vitali Tatarintev