...
- Red Hat is migrating its existing Jira, Jira Service Management (JSM), and Confluence Data Center instances to Atlassian Cloud.
- The migration is structured as an initial "lift and shift" of current tools and compatible third-party applications, followed by a future focus on modernization.
- Primary drivers for this migration include enhancing efficiency, reducing time to value, increasing performance reliability, and a more streamlined user experience.
- Our main objective is to ensure the migration does not introduce unintentional regression of functionality to any user.
When is the migration?
- Go-live is Monday, March 16. The migration will take place either March 7-8 OR start sometime on the afternoon or evening (NA-time) on Friday, March 13 and continue through the weekend (March 14-15.
The migration will take place over the course of a weekend). During that weekend and after migration, our current Data Center instance will become read-only.The exact migration weekend depends on completion of the upcoming round of User Acceptance Testing and the resolution of any bugs categorized as blockers by the migration team.
Who is impacted?
- All users of Jira (issues.redhat.com), Confluence (spaces.redhat.com), and Jira Service Management across Red Hat, including project owners and admins, and collaborative partners will migrate to the new Atlassian Cloud instance.
...
- After migration, you will log in using your primary company email address (the one you use for your internal company systems), not your current @redhat.com email.
- Partners who wish to retain their Jira account history (comments, created issues, assigned issues, and other related data) tied to their current @redhat.com account, will need to share their primary company email address with us. Look at for a communication with more information.
- More details on the justification for why partners need to use their company email addresses to log in, is documented in our User Account Policy here.