Perform a CQA 2.0 analysis of all content that is going to be migrated to DITA. For instructions on how to do the analysis, see the CQA 2.0 template.

You need to address all problems on the Pre-migration tab in the CQA 2.0 document prior to the migration. You can finish the required/non-negotiable items from the Quality tab after the migration to AEM concludes.

Acceptance criteria:

• You have reviewed all currently supported content using a copy of the CQA 2.0 document.
• You have filed and fixed bugs for all items on the Pre-migration tab of the CQA 2.0 that don’t meet criteria.
  • You have put these bugs in a new epic called Phase 0: $YOUR_PRODUCT CQA 2.0 content review.
  • You have filed only one epic for all these bugs; it will be used to track progress. 
  • You have added the CQreview_pre-migration label to the Phase 0: $YOUR_PRODUCT CQA 2.0 content review epic.
• You have made the Phase 0: $YOUR_PRODUCT CQA 2.0 content review epic a child of your tracking Feature ticket under DOCS-2663 (same parent as for the existing Phase 0: $YOUR_PRODUCT pre-engagement work for AEM migration epic.)
• You have filed bugs for all items on the Quality tab of the CQA 2.0 that don’t meet criteria.
  • You have created one or more epics for the required/non-negotiable ones and add the label CQreview_non-negotiable to these epics.
  • There are no requirements on the epic naming or linking.
  • These bugs do not have to be fixed before the migration.

Additional information:

• DITA Migration Jira Tracking Guidance Confluence page

  Who is your target persona?
  

  <Role>
  

  What stage of the user journey are you targeting?
  

  <User journey>
  

  Why is this content important?
  

  <Justification>
  

  What is the main user goal aka job to be done?
  

  As a <role>, I want to <goal>
  

  What high level steps does the user need to take to accomplish the goal?
  

1. <User steps to accomplish goal>
   

What pain points are the user likely to encounter when accomplishing this goal?

<Pain points>

Links to existing content

• <Add link to content>
  

People:

• SME: <SME>
  
• QE: <QE>
  

Release Note: Yes/No

Documentation Outline

• <Documentation outline>