GitLab status emails for a particular outage should use the same email thread
This issue doesn't seem to fit in any of the templates above. I am subscribed to well over a dozen status emails for the the products my company uses. GitLab is literally (the actual definition of literally here) the ONLY company that does not reuse emails threads for updates about a given issue (I mean, y'all don't use email threads at all). This is inundating my inbox with emails and makes it hard to track when/if an issue on GitLab is fixed.
Also, while you're in there, can you make the email subjects actually useful? Today, when I woke up, I had 14 emails all with the same title "Status Notification from GitLab System Status". Which parts of the systems are broken or fixed? How could anyone know without spending an exorbitant amount of time manually sorting and reducing emails, which I did.
14 separate email threads for 3 issues!!! It should've been 3 threads, with useful subjects. Maybe a couple more if the scope of them changed for a new subject (and even then you could still use the same thread). But, in this case (after an investigation that took tens of minutes and takes seconds with every other status email I get), the scope of none of them changed, so it should've been 3 emails threads.