Summary of the change

Before the migration, 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


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 Key

New Space Key

AMR TeamATATP
CMS RebuildCRCRP
Contact TracingCCTCCTP
Corporate PerformanceCPCPP
Crisis ControlCCCCP
Demonstration SpacedsDSP
Development SpaceDC

DCP

Digital MarketingDMDMP
Digital PSBCsDPDPP
Epidemiology and SurveillanceESESP
FNP DataFDFDP
Health Care TeamHCTHCTP
ImmFormIM

IMP

Incentivisation ProjectIP

IPP 

Infrastructure Test & TraceITTITTP
SHAPESTSTP
Specialised Commissioning Public Health NetworkFPFPP
Technical ArchitectureTATAPP
Tri-Directorate January 2017 Digital PaperTDPTDPP
  • No labels