> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/overview/changelog/2026/week-of-2-nov-2026.md).

# Week of 2 Nov 2026

Decube releases from 2 Nov 2026 to 8 Nov 2026.

{% updates format="full" %}
{% update date="2026-11-03" %}

## 1.63.0: Jira Work Items

#### Feature Release: Jira work items for Data Quality V2 cases

You can now send Data Quality V2 cases to Jira as work items, so the people who fix data problems pick them up in the Jira queue they already use. Create a work item from a case while you triage it, or add Jira as an alert channel so a rule creates one for every new case on the monitors it targets. See [Jira work items](https://docs.decube.io/data-quality-v2/cases/jira-work-items) and [Jira alert channel](https://docs.decube.io/data-quality-v2/alerts/alert-channels/jira).

* **\[Data Quality V2]** Cases: create Jira work items from **Case details**, choosing the project, Work Item type, assignee, summary and description. The description opens pre-filled with the case, monitor and affected assets. A case can link up to 10 work items, in the same project or different ones.
* **\[Data Quality V2]** Cases: track every linked work item's status, key and assignee on the case, change its summary, description or assignee, or unlink it. A **Jira Linked** badge shows next to the case status.
* **\[Data Quality V2]** Alerts: Jira is now an alert channel. Pick a project and Work Item type, build the summary from `{{MonitorName}}`, `{{CaseId}}` and `{{MonitorId}}` tokens, and choose what happens when a new incident joins a case that already has a work item: do nothing, create a new work item, or add a comment to the existing one.
* **\[Data Quality V2]** Status sync (optional): once you map a project's statuses and register the Jira sync webhook, the first linked work item to reach a status mapped to Close closes the case.
* **\[Data Quality V2]** Audit History is now a dedicated tab on the case. It records Jira work items added by a person or an alert rule, work items removed, and cases closed by Jira.
  {% endupdate %}

{% update date="2026-11-02" %}

## 1.62.5: Data Quality V2 in MCP and Trusty AI

#### Feature Release: Data Quality V2 in MCP and Trusty AI

The Decube MCP server and Trusty AI now work with Data Quality V2. Their data quality tools read and manage V2 monitors, cases and incidents, and the Data Quality Classic tools are removed. Classic monitors and incidents are no longer available through MCP or Trusty AI.

* **\[MCP]** Monitors: search by asset, type, schedule, status or last run state; read a monitor's configuration and run history; check which monitor types and detection options an asset supports; create, update, run, enable, disable and delete monitors.
* **\[MCP]** Cases: search by monitor, asset, assignee, state or incident date; read a case's incidents with their evidence and debug query; assign, unassign, mute, unmute or close a case.
* **\[MCP]** Quality scorecard: generate a Data Quality Scorecard V2 report for a source over a date range, then read its results.
* **\[MCP]** Removed `get_quality_summary`, `get_monitor_history`, `get_monitor_run_status`, `update_monitor`, `run_monitor`, `list_incidents`, `get_incident_history` and `update_incident`. `get_incident_details` now returns Data Quality V2 incidents.
* **\[Trusty]** Trusty AI answers data quality questions from Data Quality V2 monitors, run history and cases.
* **\[Skills]** Updated eight Decube skills to use the new tools: Incident Remediation, Monitor Recommendation, Steward Morning Brief, Quality SLA Tracker, Query-Safe Table Finder, Dashboard Trust Check, Pipeline Impact Check and Schema Drift Watch. Re-download them from the Skills page to replace older copies.

#### Bug Fixes

* **\[My Account]** Fixed an issue where Data Sources option menu items on the Integrations page were truncated.
* **\[Data Quality V2]** Fixed an issue where read-only accounts could access the Action button on Templates.
* **\[Lineage]** Fixed an issue where selecting a column on a second node orphaned all other nodes on the canvas.
  {% endupdate %}
  {% endupdates %}
