Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Users impacted:


  • All current users of Confluence spaces across UKHSA, PHE, Test & Trace domains
  • External users including partners and vendors

What you should expect:


  • Minor changes to resolve domain conflicts before the main migration - impacting some Confluence spaces only
  • An updated App offering - this will involve some change and updates to the add-ons currently integrated with Confluence, to view changes in detail see Confluence: Apps, Integrations and Plug-ins-Detailed Changestbc

Migration approach:

  • Migration of data within Confluence will take place over three phases; PHE, NTBS and Halo/T&T
  • Conflicting project keys will require fix before migration to Cloud (see below)

T-Minus Plan for Jira and Confluence 

View file
nameT-Minus PlansPHE.pdf
height250

View file
nameT-Minus PlansHalo.pdf
height250


  • tbc

Pre-Migration Changes 

Summary of the change

Before the PHE, NTBS and Halo Confluence data can be consolidated onto the single UKHSA Cloud platform, there are a several data conflicts that need to be fixed.

In Confluence, these conflicts occur where there are duplicate Space Keys (the unique identifier for the Space). 

What does this mean?

The following items will be fixed as part of the fix process and will be tested as part of UAT:

  • page history
  • comments
  • blogposts
  • attachments
  • users/authors
  • links to other pages/spaces
  • links to Jira tickets
  • macros
  • page restrictions
  • page permissions
  • add-on macros (e.g draw.io etc.)

ALERT TO IMPACTED USERS

Please consider the following if you use any of the Confluence Spaces below:

  • Do you use any hard coded links to the Spaces that we are changing (e.g. URLs in the page content or comments)? If so, these will need to be updated manually.
  • If you use the Jira Issue macro in Confluence you will experience a period of time where custom user macros will not be updated. This will be fixed but you will need to allow some time for the cache to be refreshed. 
  • If you use any API with the space key you will need to update your REST Calls

Get Involved!

If you have any concerns or questions about this change, or would like to volunteer for User Acceptance Testing (UAT), get in touch here

You can also come along to one of our drop-in sessions - every Thursday at 12:00



Post-Migration Changes




Contains full impact maps and changes.

Which Confluence Spaces are impacted?

The Spaces that are required to undergo a change in Space Key are listed below.

Confluence Space Name (current PHE)Current Space KeyNew Space KeyAMR TeamATATPCMS RebuildCRCRPContact TracingCCTCCTPCorporate PerformanceCPCPPCrisis ControlCCCCPDemonstration SpacedsDSPDevelopment SpaceDC

DCP

Digital MarketingDMDMPDigital PSBCsDPDPPEpidemiology and SurveillanceESESPFNP DataFDFDPHealth Care TeamHCTHCTPImmFormIM

IMP

Incentivisation ProjectIP

IPP 

Infrastructure Test & TraceITTITTPSHAPESTSTPSpecialised Commissioning Public Health NetworkFPFPPTechnical ArchitectureTATAPPTri-Directorate January 2017 Digital PaperTDPTDPP