Issue Summary

It is possible to see different sets of incident templates when viewing through the UI, vs querying the API

Steps to Reproduce

1. Create some incident templates through the UI.

1. View the list of incident templates

1. In the database, edit the group_id for one of the templates, to a random number.

1. In the UI, the incident template that was edited no longer shows in the list of incidents.

Expected Results

Incident template is no longer present in the UI or API, or is pulled out of the invalid group and visible in both the UI and API

Actual Results

An incident template that doesn't belong to a group should have a group_id of nil, but some templates are getting into the state where they have a group_id of a group that doesn't exist. When we render the page, we first show 'ungrouped' templates, and then we show groups of templates. I'm not sure how they're getting into this state, I tried a few ways but couldn't get it to happen. It's happening though, because we had support tickets of people stuck in this state. This bug does not affect the API, because it just does a query for all the templates belonging to that page and returns them to you.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available