Release v20210603

This is the first release of June!

Features:

• Adds the ability to set a projects label color (#1151)
• Adds the ability to filter incidents by their associated tag types (via associated tags) (#1177, #1182)
• Adds the ability to filter incident table and incident export by reported at date window (#1265)

Improvements:

• Makes CSV export of incident data more reliable (correctly escaping incident descriptions) (#1152)
• Adds settings breadcrumbs to make it easier to switch between projects (#1153)
• Refactors slack update incident dialog to a modal and adds the ability to specify incident tags (#1175)
• Improves participant management during the incident/participant lifecycle (#1179)
• Removes deprecated plugin enabled kwarg (#1186)
• Alters when new tasks are created, we no longer automatically create new incident tasks if the incident is closed (#1199)
• Refactored github actions (#1221) Thanks @vj-codes !
• Improves how the /dispatch-list-incidents command handles projects (#1225)
• Allows project roles to be assigned via the CLI (#1243)
• Don't attempt to send feedback to archived channels (#1244)
• Adds a constraint ensuring that tags must have a tag type associated (#1255)

Bug Fixes:

• Fixed an issue with a migration where only some engagement filters where created (#1164)
• Fixed an issue where you couldn't both search and filter incidents at the same time (#1178)
• Fixed an issue with documentation creation in the UI that would clear associated filters (#1188)
• Fixed an issue with how checkboxes were displayed in the incident priority UI (#1187)
• Sets service_id if a participant is reactivated (#1216)
• Fixed an issue where multiple extraneous participant roles were being created (#1222)
• Fixed an issue where participant engagement can be accidentally overridden (#1227)
• Fixed an issue there incident type visibility was not available to be updated via the Dispatch UI (#1254)
• Fixed an issue where incident visibility would become unset when modified by /dispatch-update-incident command.
• Fixed an issue with the dispatch plugin list command (#1266)

Documentation:

• Fixes link to plugin documentation (#1184, #1184)

Release v20210506

This is the first release of may and it's a big one!

With this release, we are now able to offer individual teams their own space to run their incidents. Per-project configuration of incident types, incident priorities, tags, notifications, plugins, etc, allows for multiple teams to use Dispatch in their own way.

This is a big change that requires extensive database schema manipulation and data migration. As always, before upgrading. backup your existing data!

Features:

• Adds organizations/projects for incident resources (#990, #1010, #1011, #1019, #1023, #1024, #1028, #1035, #1036, #1040, #1047, #1050)
• Adds the ability to select FAIR Form of Loss category for incident types (#979)
• Adds a helpful direct message to the new incident commander (#1046)
• Adds the ability to scope tags by tag type while filtering (e.g. "applications/" will list all tags with tag-type of "applications") (#1067)
• Adds the ability to bulk delete incidents via web UI (#1069)
• Adds the ability to filter incidents by their tags (#1106)

Improvements:

• Consolidates restricted visibility-based filtering (#995)
• Moved from ace to monaco code editor (#1012)
• Makes company field optional for individual and team in Web UI (#1064)
• Unified web UI selects/combobox to include "load more" option (#1062, #1076)
• Creating a new search filter will automatically add it to the focused notification (#1066)
• Adds default column to incident priority table (#1090)
• Adds more response messages to slack modals and commands (#1132)
• Converts engagement filters to search filters (#1070)
• Updates individual contact info if it exists (#1129)
• Lots and lots of dependency updates

Bug Fixes:

• Fixes bug where the incident role was not being displayed correctly when changed via the Web UI (#1002)
• Fixes missing validation prop that prevented new individuals from being created in the UI (#1032)
• Fixes issue for incident reporter being incorrectly reported via API (#1055)
• Fixes issue where reporter/commander could not be changed if there was no incident conversation (#1054)

Documentation:

• Reworked a large amount of the documentation (#1088)

Security

• Fixes URL sanitization to prevent XSS (#1126)

Release v20210319

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)

Release v20210224

This is the third release of February.

Bug Fixes:

• Missing parameter for dispatch-core contact plugin (#886)
• Checks for the existence of a documented plugin before displaying document loading bars in the UI (#887)
• Allows for all incident types to be view in incident type select dropdown (#895)
• Fixed a saved search schema issue (#897)
• Fixed an issue with socket mode events (#899)
• Sending tactical reports to tactical groups (instead of notification groups) (#900)
• Fixed issue with user role modification via the UI (#906)
• Fixes issue where incident new/edit window was displayed for summary tables (#907)
• Fixed an issue - showing up in google docs task ids (#911, #915, #917)
• Removed renounced roles from participant view in UI (#913)
• Fixed issue with commander/reporting not displaying in incident detail view in the UI (#914)

Improvements:

• Frontend sentry configuration improvements (#880, #881)
• Adds incident commander team name to conversation topic (#883)
• Removes updating external tickets from cost job (noisy) (#889)
• Allow special characters to be used in Postgres passwords (#898)
• Jira plugin now supports cloud and on-prem hosting (#901)
• Adds CLI command to uninstall plugins (#904)
• Adds description and reporter to welcome message, and list resources message (#908)
• Aligned user table action buttons in the UI (#909)

Documentation:

• Improvements to large sections of the documentation, fixing images, and improving grammar. (#905)

Release v20210212

This is the second release of February.

Special thanks to @sfc-gh-pkommini, @rilutham, and @dk0r for various issue reporting and discussions.

Bug Fixes:

• Fixes issue with incident details constantly re-rendering (#845)
• Fixing issue with block actions (#847)
• Removing old table reference (#848)
• Check if incident exists before sending feedback to user via Slack (#849)
• Adds missing key value pair for feedback button (#850)
• Pinning spacy to avoid breaking changes (#851)
• Guards against bad path data (#853)
• Fixing the way Slack events are handled (#854)
• Allowing for channel event items (#855)
• Fixes issue with Slack channel reactions (#856)
• Fixing an issue with updating user roles (#858)
• Fixing an issue with incident priority update permission (#862)
• Re-adds logic to send executive report to notifications group (#872)

Improvements:

• Improves tracking only and new document fields language (#846)
• Removes visibility open check before sending incident created and updated notifications (#852)
• Updating example data and making some config items optional (#857)
• Accessing enum value attribute (#860)
• Makes email notifications more compact (#868)

Features:

• Adds support for incidents daily report notification via email plugin (#859)
• Adds support for incident daily reports based on notification filters (#865, #869)

Release v20210210

This is the first release of February.

Special thanks to @sfc-gh-pkommini and @rilutham for various issue reporting and discussions!

Bug Fixes:

• Updates and fixes core jira plugins (#711) Thanks @sfc-gh-pkommini!
• Fixes task table loading on error (#774)
• Fixes issue where tags were not filterable in the dashboard (#775)
• Fixes issue where with timeline slack modal (#813)
• Restricts sensitive configuration items to admins (#810)
• Fixes direct linking of incidents (#803)
• Fixes login redirect issue when using basic authentication (#791)
• Fixes issue where tasks from sensitive issues could be viewed (#790)
• Fixes issue where node binary was not available within the image (#835)

Improvements:

• Centralizes and improves permissioning system (#811, #822, #821)
• Sets a default provider for Dispatch UI (#809)
• Improves the date formating in email notifications (#798)
• Incident creation hardening (#785)
• Added additional color to incident type graph color palette (#781)
• Assignment name alignment (#840)
• Adds password reset CLI command (#826)
• Un-slackifies daily summary (#819)

Features:

• Slack socket mode (#805, #799, #795)
• Incident notifications (#834, #830, #829, #828, #825, #824, #802, #786, #777)
• Saved search filters (#841, #837, #836, #832, #818, #801, #787)
• Adds tactical and executive report creation to Dispatch UI (#839, #838, #823, #820)

Documentation

• Fixes broken images (#804)

Release 20210112

This is the first release of January and of 2021!

Bug Fixes:

• Fixes potentially unsafe HTML URL links (#717)
• Fixed an issue where incident export would have issue exporting null values (#723)
• Fixes issue with some selects attempting client side filtering in Dispatch UI (#729)
• Don't attempt to re-add participants if their task has been resolved (#731)
• Fixes an issue with displaying multiple error messages in Dispatch UI (#762)
• Only reactivate incident when status goes from closed to active (#765)

Improvements:

• Improved on-call plugin related warnings (#713)
• New Dispatch UI color scheme based of the hawkins design language (#715)
• Aligns our use of incident command and incident reporter to rely on "participant" object instead of "individual" objects (#730)
• Restrict incident slack commands from some participants (#732)
• Refactor/convert HTML emails to MJML templates (#735, #750, #756, #760)
• Standardised filter button text (#752)

Features:

• Adds dark mode to Dispatch UI (#720)
• Adds treemap chart for incident tags (#722)
• Allows incidents to be deleted. Note: this only applies to the Dispatch DB and not to external resources (#727, #748)
• Adds task CSV export (#733)
• Adds timeline CSV export (#734)
• Adds a modify user role command to the Dispatch CLI (#737)
• Adds "tracking only" checkbox to incident report form (#761)

Release 20201207

This is the first (and only) release of the month of December. Major changes include:

Bug Fixes:

• Fixes an issue in pagerduty plugin, when faced with a page without an incident name (#690)
• Fixes an issue where route context was not optional (#695)
• Fixes an issue where the oncall summary was calling the oncall plugin incorrectly (#697)
• Fixes an issue with the external syncing of task data (#700)
• Fixes an issue while calculating report reminders (#701)
• Fixes an issue with searching while sorting and receiving inconsistent results (#701)
• Fixes an issue displaying incident tags (#705)

Improvements:

• Adds support for cc'ing in email comms (#687)
• Adds support for cc'ing the incident response team in daily feedback digests (#688)
• Tweaked response message when running the /dispatch-engage-oncall command (#691, #692, #704)
• Condensed navbar in the Dispatch UI (#694)
• Adds a description column to the service table UI (#699)

Features:

• Adds support to build edit incidents (#689)
• Adds incident export wizard (to csv) (#698, #703 )

Documentation:

• Added workflow slack command documentation (#693)
• Added additional participant engagement documentation (#696)

Release v20201119

This is the second release of Dispatch in the month of November. Major changes include:

Security:

• Fixes an issue where a non-admin user may be able to filter/search for restricted incidents. (#659)

Bug Fixes:

• Fixes issue where updating a task status in the Dispatch UI would not update the external task status (#663)
• Avoid the creation of duplicate db_session (#664) Thanks @liamvdv !

Improvements:

• Harden the incident creation flow against misbehaving/misconfigured plugins (#662)
• Modifying the language sent to incident commanders on incident close to close any outstanding incident tasks (#669)
• Adds incident visibility to the incident creation receipt (#671)
• Improved default sorting for feedback table (#675)

Features:

• Adds an "evergreen" email notification to documents, allowing users to remind themselves to review runbooks. (#660)
• Adds the ability to automatically map service to the liaison role for a given incident type. (#661)

Documentation:

• Fixed various documentation typos (#665, #667) Thanks @roandudel !
• Added better release documentation (#679)

Release v20201106

This is the first release of Dispatch in the month of November. Major changes include:

Security:

• Fixes issue where regular users can join restricted incidents (#649)
• Fixes issue where a user can register an account as admin (#650)
• Filters restricted incidents for non-admins (#651)

Bug Fixes:

• Fixes error message in update_user() function in auth views module (#648)
• Adding better checking for non-existent tab data (#652)
• Adds an error message when the incident can't be reported (#653)
• Ensures the stable flow runs for incidents opened as stable (#654, #656)
• Fixes filtering on several columns (#655)

Improvements:

• Makes tag type description optional (#647)
• Adds incident title to feedback Slack direct message (#657)

Documentation:

• Added production deployment documents (#658)