Moving issue tracking to GitHub

[Chris Cranford]

Hi Everyone!

As part of Debezium's transition to the Commonhaus Foundation, we're evolving how we track issues and plan work. Starting in December 2025, Debezium will move from the Red Hat Jira [1] instance to GitHub Issues [2] as the canonical place for reporting bugs, requesting features, and following all ongoing work.

Key points:

    - December 11th: Open Jira issues will be migrated to GitHub.
    - December 11th-19th: A short transition period where new Jira issues will be manually moved to GitHub.
    - December 19th: Jira transitions to read-only mode; GitHub Issues will become the single source of truth.

We will migrate only essential information (title, description, components) and link each Jira ticket to its corresponding GitHub issue, so history remains accessible. Closed Jira issues will remain in Jira as historical records and will not be migrated.

This change brings issue tracking and management closer to where conversations, pull requests, and our day-to-day development occurs. In addition, it aligns Debezium with our foundation-driven governance while also simplifying the contributor experience for the community.

We are grateful to Red Hat for hosting our Jira project for many years, supporting Debezium's growth, and we're excited about this next step and look forward to continuing this journey with the community.

For more details: https://debezium.io/blog/2025/12/01/changing-issue-tracker/

Thanks,
Debezium project team

[1]: https://issues.redhat.com/project/DBZ
[2]: https://github.com/debezium/dbz/issues