Jira Cloud migration: Difference between revisions
AlexBlasche (talk | contribs) No edit summary |
AlexBlasche (talk | contribs) No edit summary |
||
| Line 32: | Line 32: | ||
== First login == | == First login == | ||
During the migration the email of each user is migrated to the Atlassian user directory and an invitation is being sent out. You have to accept the invite which ultimately leads to an Atlassian login prompt | 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. | |||
[[File:Atlassian Login prompt.png|thumb|border|none]] | |||
=== Using qt.io Email address === | === 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 === | |||
When you log into the system please update your profile and personal settings. | |||
[[File:Account details.png|none|thumb]] | |||
Revision as of 13:24, 30 July 2025
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.
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
When you log into the system please update your profile and personal settings.
