ITTN-051: Moving Jira Software On-Premise service to Atlassian Jira Cloud

  • Iain Goodenow

Latest Revision: 2021-09-13

Note

This technote is not yet published.

To Move Jira Projects from Tucson On-Premise to Atlassian Jira Cloud

1   An Evaluation of Projects

  • Will it Move to Cloud or Retired/Deleted
  • Is it only for Construction
  • Will it move to Operations
  • Plan to transition to NOIRLab Jira

3   Our Jira Cloud Instance

  • RubinObs has a Cloud Instance is Jira Software: http://rubinobs.atlassian.net/
  • List of Site Administrators to manage the cloud instance and all projects within

4   General Topics

  • Outage of General Services
  • Outage Isolating the Base-Summit from Jira Cloud
  • Migrating to another Jira-Like Service
  • Backups of our Data in case of lock outs
  • Security and User Groups

5   What Directory Service(s) are we to use?

Examples Existing AD-Tucson, Atlasian, AD-NOIRLab, Github, Google, combinations of these or others

5.1   Considerations

  • Existing Users are mostly Crowd-AD - No Direct Crowd Users; bridges to AD-Tucson
  • Some local Jira Users (same with Confluence)
  • Not all users of Jira have Github or G-Suite profiles/accounts
  • Not all users are within the AURA/RubinObs Ecosystem
  • Plan on transfer to NOIRLab Jira

5.2   Investigate

  • Continue with AD-Tucson in cloud? - Requires isolated RODC in DMZ (safe enough?)
  • Can group membership support contain users from various Directory Services (been a problem with Crowd)
  • How will the Project structure groups to improve the method used today?
  • Use 2FA for site changes or sensitive projects?

6   Move all Projects “At Once” or “One-At-Time”

  • Evaluate the different methods

7   URL Redirect

  • Will Issue links from On-Premise Map Well to Cloud Instance
  • Is simple CNAME Record sufficient or Map-Rules required

8   Backup and Recovery

  • Any concerns about billing and account lock out?
  • Ransomware affects Cloud
  • Extended Outage when Summit/Base/Operations is in maintenance or operation mode

9   Tasks

  • Define List of Stakeholder Groups and Rep(s)/Liaison(s) DM-SQRE Frossie E, SE Austin R, Camera ?, PMO Budget and Schedule ?, Pre-Operations Bob B, NOIRLab Chris M, General Users ?, Consumer agents, bots, or services?, Others ?

9.1   Prepare Test Migrations

  • Owner of Site should prepare a document of actions/tests for IT to perform as first check
  • Owner of Site should have Acceptance Requirements
  • Owner of Site should prepare the project for migration
    • Project may fail pre-flight and action will be required
    • Purge non-essential data

9.2   Configure Infrastructure for Directory Service(s)

  • This may be required before testing or only to prepare for migration
  • Test the various login methods
  • Test various access and group membership of those logins
  • What sort of “sync” between the Directory Service Account and Jira Account Profile
    • If I login as iaingoodenow to the account using AD igoodenow in Jira project X
  • Get a list of Local Users of Jira (and Confluence)
  • What about DB Logins like JiraRO used by GC (not sure who now)?

9.3   First-Attempt Migrations

  • Basic Import Process and Tests
  • Acceptance Tests to Perform
  • Develop FAQ
  • Need a list of which Add-ons / project?

9.4   Prepare and Execute All or Iterate the Actual Migration

  • Formal Testing - Stakeholders/Owners need to exercise the work flow and overall functionality
  • Need to Know New Link Locations - How to Handle Communication from IT and Owners to Stakeholders

9.5   Close out old system

  • No project should exist
  • Assumed data will be purged and guest deleted