Product update

Incident kanban view, email notifications & reference urls

Incident kanban view, email notifications & reference urls
by
Nick Freund
April 9, 2024

Today we are shipping a number of updates to our flagship data incident workflows. These include a new kanban view for incidents within our web application, email notifications, reference urls and fixes to customer reported issues.

Data incident kanban view

Incident kanban view

We now support a kanban view for your data incidents, so that you can understand and manage your incident landscape visually. 

Email notifications for incidents:

While being notified of your incidents via Shared slack channels continues to be our most popular feature, there are many reasons that users might want email notifications. For example, we have spoken with teams that want to take advantage of our dbt incident alerting, but do not use Slack. 

Now, we support email notifications for when incidents are created and updated in our system. If you wish to turn these off, please visit your notification settings here and toggle them off. 

Reference urls

In addition to our existing JIRA integration, you can now link Workstream incidents to other systems via reference urls. Use cases include other agile tools like Linear, or more traditional incident management solutions like PagerDuty or OpsGenie. 

Note: we are building a group of design partners for a native Linear integration, so if this sounds interesting please reach out or email us at support@workstream.io.

Edit and update your dbt Cloud connection

There have been numerous instances where clients need to reconnect dbt Cloud, and/or provide us a new dbt Cloud token. Previously you had to open a support ticket, but now you are able to manage this yourself via our UI.

Fixes and enhancements:

We are also shipping a series of fixes and enhancements to issues reported by customers, including:

  • We now create incidents for when dbt models fail to build (ex: model timeout), in addition to when your dbt tests or freshness checks fail.
  • In our web application, we now truncate long dbt test names so that they don’t break our UI. You can view the full test name via a hover state.