This is the first release of March. The highlights of this release are a new flexible forecasting that allows you to forecast incidents based on incident type, incident priority or tag, and the ability to define and add new cost types/ forms of losses other than the default, computed response cost to incidents. Major changes in this release can be found below.
Features:
- Adds support for non-operational costs (#928, #947, #949, #952, #963, #964)
- Adds support for suggesting tags for a given incident based on existing tags (#934)
Improvements:
- Adds protections for restricted incident types restricted (#921)
- Ensures the mjml is installed correctly on the core image (#923)
- Ensures re-resolving services doesn't result in multiple engagements (#924)
- Silencing warnings until they are fixed upstream (#927)
- Updating configuration documentation RE: MJML_PATH (#929). Thanks @AlexaKelley!
- Adds column for liaison service in incident type table (#938)
- Allows for more flexible forecasting (#941)
- Forcing PostgreSQL v12 in docker-compose file (#942)
- Do not send incident report reminders if incident status hasn't changed (#948)
- Improves text and formatting of information review reminder (#950)
- Slack documentation improvements (#966). Thanks @klarrio-dlamb!
- Allows for individuals to have unique external IDs associated with them (#968)
- Allowing external id in nested views (#969)
Bug Fixes:
- Fixes API query param names in multiple view modules (#922)
- Fixes URL for example env (#931). Thanks @Cull-Methi!
- Fixes text in daily report context section (#933)
*Various minor spelling corrections (#936). Thanks @homebysix! - Disables nested validation observers when creating new or editing existing incident types (#939)
- Lots of dashboard fixes (#943)
- Check incident status before sending messages to conversation (#951)
- Adds missing incident deletion cascades (#965)
- Fixing issue with filtering forecast based on tags (#970)
Security:
- Ensure that an individual contact can't be hijacked (#926)