You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like to take a staged approach here. As the first stage, I'd like to just link from the Incident page to the relevant section in the wiki. That's trivially easy, and it gets us the important win of providing users with easily-updatable descriptions of the Incident Types.
The right long-term solution is what this issue describes, i.e. add a DESCRIPTION column to the INCIDENT_TYPE table, add some way to set/edit values for that column (on the admin incident types page?), and have some way for the UI to display all those descriptions (as a new page in the legacy web client?).
The long-term solution is a fair bit more involved, and less likely to be prioritized in the near-term. The link-to-the-wiki solution is a pretty good band-aid, with minimal downsides.
This is a trivial band-aid solution relating to #239.
I observed out there as a first-time Operator in 2024 that
many Incident Types are non-obvious.
#1413#239
This is a trivial band-aid solution relating to #239.
I observed out there as a first-time Operator in 2024 that
many Incident Types are non-obvious.
#1413#239
The
INCIDENT_TYPE
table could use aDESCRIPTION
column (text) into which we could put a description of what incidents that type is meant to apply to.We could then add that into to the application as a way to better document the incident types.
The text was updated successfully, but these errors were encountered: