Hi Dispatch users!
We've been busy working on Dispatch since the last release in September and this release comes with a ton of new useful features, improvements, and bug fixes across the app. Here are some that are worth highlighting:
- Allowing to define and set incident severities to represent the measured impact resulting from an incident.
- Allowing to assign a new participant role called Observer to improve accuracy of incident cost calculation. Incident participants that get resolved via engagement filters and added to the incident on incident creation or modification will be assigned this role. Time spent on this role won't be counted against incident cost. Individuals with this role will get the role converted to Participant if they send 10 or more messages to the incident channel.
- Allowing to view signal instances associated with a case.
- Ability to report cases via intake form at https://dispatch.example.net/default/cases/report.
- Allowing to configure client settings via an API call.
Give it a try and let us know what you think. Thanks to all community members for your continuous help and support!
Enhancements:
- Shortens task notifications text and converts notifications to ephemeral to reduce noise in incident channels (#2679) by @mvilanova
- Forces the user to specify the incident project (#2673) by @kevgliss
- Don't attempt to sync triggers automatically on database upgrade (#2666) by @kevgliss
- Allows to configure client settings via an API call (#2664) by @kevgliss
- Adds a settings filter for project settings (#2659) by @kevgliss
- Disables Run Workflow option if incident is closed or case is escalated or closed (#2655) by @mvilanova
- Renames moderate severity to medium severity (#2654) by @mvilanova
- Moves signal definitions to its own settings section (#2653) by @mvilanova
- Allows to view signal instances associated with a case (#2643) by @kevgliss
- Uses vite to build the frontend (#2637) by @kevgliss
- Adds section for commander paged in the incident report receipt card (#2636) by @mvilanova
- Announces when participants are assigned the observer role in the incident channel (#2634) by @mvilanova
- Improves participant role's activity (#2633) by @mvilanova
- Enhancements to signal deduplication (#2631) by @kevgliss
- Adds support for a new incident observer participant role (#2625) by @mvilanova
- Pre-fills mapped incident type in case type in escalate case form (#2619) by @mvilanova
- Disables escalate option and button when case is escalated or closed (#2618) by @mvilanova
- Reorganizes UI Panel (#2609) by @mvilanova
- Adds support for incident severity (#2608) by @mvilanova
- Allows for tasks to be specifically excluded (useful for scheduling signals) (#2589) by @kevgliss
- Adds support for visibility in SearchFilter (#2587) by @jneelamekam
- Shortens total response hours widget label (#2565) by @mvilanova
- Hides escalate option and button if case is already escalated or closed (#2564) by @mvilanova
- Deprecates relationship between task and ticket (#2563) by @mvilanova
- Enhances case management workflows (#2550) by @kevgliss
- Allows to load more than five incident types (#2548) by @mvilanova
- Shows related cases in the incident details tab (#2546) by @mvilanova
- Allows to load more tag types (#2545) by @mvilanova
- Improves logging configuration (#2544) by @mvilanova
- Enhances the case escalation modal (#2541) by @kevgliss
- Enable case types in one project to be mapped to incident types in any project (#2540) by @mvilanova
- Adds case reporting support (#2536) by @kevgliss
Bug Fixes:
- Fixes validation that allowed multiple FAQs to be defined (#2681) by @kevgliss
- Adds correct resource type when FAQs are created (#2680) by @kevgliss
- Adds a case cascade to signal instances to allow for the deletion of cases (#2678) by @kevgliss
- Updates the node version included in the docker file (#2677) by @kevgliss
- Ensures we only show enabled incident types (#2670) by @kevgliss
- Removed resource weblink resource validation as web link is not necessarily a URL (#2669) by @kevgliss
- Active cases and incidents respect project filter query argument (#2668) by @kevgliss
- Allow for 100% sampling rate (#2667) by @kevgliss
- Ensures that filtering is only enabled for project settings subMenu's and not others (#2665) by @kevgliss
- Adds missing incident severity to daily incidents report (#2663) by @mvilanova
- Sorted tasks by creation date (#2658) by @jneelamekam
- Closes db sessions when we're done with them to prevent having idle sessions (#2650) by @kevgliss
- Check incident visibility before allowing individuals to join or subscribe to an incident (#2649) by @mvilanova
- Always ensure there is a fingerprint for each signal (#2641, #2642) by @kevgliss
- Fixing import and database revision branches (#2640) by @kevgliss
- Sorted PD Schedule names (#2635) by @jneelamekam
- Vue sentry fix (#2632) by @kevgliss
- Disables dropping search triggers and functions (#2613) by @mvilanova
- Fixes null values in case reporting form and allows for url updating and copying URL to clipboard (#2576) by @kevgliss
- Sets the triage_at time when case is escalated via UI modal (#2568) by @mvilanova
- Uses the 'simple' dictionary to provide better search consistency (#2559) by @kevgliss
Documentation: