Issue Summary

Following migration of Confluence content from server to cloud, it is found some time macros are in form:

<time datetime="2022-3-7" />

These do not render as Confluence Cloud is expecting.

<time datetime="2022-03-7" />

This is reproducible on Data Center: Yes, intermittent

Presumably this also happens for Confluence Cloud with space import from Confluence server, wherever the erroneous content can be reproduced

Steps to Reproduce

1. Adjust Confluence system settings to yyyy-M-dd
2. If necessary, adjust user OS and browser settings
3. Create Confluence page content with date macro

   <time datetime="yyyy-M-d" />
   

4. Migrate content using CCMA
5. Observe migrated page in Confluence Cloud

It is noted this is difficult to reproduce due to CONFSERVER-40087: Date picker macro doesn't use specified date format

Expected Results

• CCMA correctly transforms date macro during migration, or
• CCMA reports on pages with erroneous macros

Actual Results

• Content is migrated, with no error thrown
• Content cannot be copied
• Content cannot be edited/published, or copied

{
  "statusCode": 500,
  "data": {
    "authorized": true,
    "valid": true,
    "errors": [],
    "successful": true
  },
  "message": "com.atlassian.confluence.api.service.exceptions.ServiceException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag </span>; expected </time>.\n at [row,col {unknown-source}]: [1,12233]"
}

Workaround

There is no known workaround.