Jira Cloud migration
This page is still work in progress.
This Page is an FAQ for upcoming migration of Qt's bug tracking system to the Atlassian cloud.
Rationale
In 2024 Atlassian discontinued the support for the Jira Server version. The only alternative option for Open Source usage is a Jira Cloud license. This means the current content from https://bugreports.qt.io must be migrated to https://qt-project.atlassian.net. After this migration bugreports will stay around as read-only reference for some time to come.
Migrated projects
The following projects were migrated to https://qt-project.atlassian.net.
| Coin (COIN) | Qt Design Studio (QDS) | Qt Tools for Android (QTTA) | Qt AS Partners Only (QTAUTO) |
| Qbs ("Cubes") (QBS) | Qt Extensions (QTEXT) | Qt Visual Studio Tools (QTVSADDINBUG) | Qt Product Management Organization (QTPMO) |
| Qt (QTBUG) | Qt Installer Framework (QTIFW) | Qt WebBrowser (QTWB) | Qt Requirements Management (QTPM) |
| Qt 3D Studio (QT3DS) | Qt Playground Projects (QTPLAYGROUND) | Qt for Python (PYSIDE) | Qt Product Installation Framework (QTPIF) |
| Qt Bugtracking interface (QTJIRA) | Qt Project Website (QTWEBSITE) | VS Code Extension (VSCODEEXT) | |
| Qt Creator (QTCREATORBUG) | Qt Quality Assurance Infrastructure (QTQAINFRA) | Qt Automotive Suite (AUTOSUITE) |
Timeline & Target
The target server is https://qt-project.atlassian.net.
| State | Status | Time Line | Description |
|---|---|---|---|
| Test migrations | Ongoing | Started on 16. June 2025 | Admin working on playbook for migration. Users cannot log into the instance yet but the Jira cloud instance is publicly visible. |
| User acceptance tests | Not started | August 2025 | Voluntary testers collect first impressions, log in and can interact with a copy of the data. |
| Final migration | Not started | Planned for September | The day when the data is moved for good and bugreports becomes read-only. |
First login
During the migration the email of each user is migrated to the Atlassian user directory and an invitation is being sent out. The invite comes from id.atlassian.com and was sent by "Alex Blasche". You have to accept the invite which ultimately leads to an Atlassian login prompt.
If the user has an Atlassian identity/account with the same email already, your existing account will gain access to an additional Jira instance. Out of the box, Atlassian already offers a couple of identity provider integrations such as Google, Microsoft & Apple. Alternatively, you may use a simple email+password combination. If this is the first time that an Atlassian login is used and none of the existing identity providers matches, you may have to select the Can't log in? option to reset the account password.
Using qt.io Email address
if you are using a qt.io email address, please choose the Microsoft Identity provider option.
Adjusting personal setup after first login into the cloud instance
Update your personal setting
If you log into the system for the first time, please update your profile and personal settings. Quite a few personal options such as profile, privacy, security, email notification & account preferences can be found behind those links.
Filter adjustments
All filters were migrated to the cloud. As a consequence some filters may be broken or a simply obsolete. Check for the following causes:
- Remove any filter which you no longer use or are unrelated to the set of projects which were moved to the cloud.
- Filter ids change during the migration as this is a running number. Therefore any JQL queries which refer to other filters should be changed such that they reference them by filter name.
- e.g. filter = 123456 → filter = "verbose filter name"
- A filter references a project that was not migrated. → Remove such project references. See the above list of migrated projects to see what is available.
- A filter references a custom field with the cf[<field id>] notation. In most cases the field ID will have changed. → Adjust the filter to the new ID
- For details see the JQL custom field documentation
- How to identify the custom ID: Use the second method highlighted by https://confluence.atlassian.com/jirakb/find-my-custom-field-id-number-in-jira-744522503.html
- The filter uses custom JQL extensions which are no longer supported. → Try to find a replacement
- Standard JQL documentation
- The Cloud instance provides a custom JQL extension via the ScriptRunner Enhanced Search plugin. Unfortunately the integration point for custom extensions has become more cumbersome as it does not seemingly integrate with the default JQL language. Please consult the documentation for the plugin.