Background

see parent feature, plus doc https://docs.google.com/document/d/1wh3CbCzmoA0EFSCGq9xmrOMvaYgNjhu_MrKfpP9-vLM/edit#bookmark=id.s1oj23v4m5o6 

Delivery notes

target 2.4 , for discussion/awareness: P1.5 should be regarded as absolutely required just not a blocker item, if it does not land, someone in BU or Eng is accountable for why it was prioritised out of the release

User Stories

P1.5 User Stories

• S2.3 [2.4 P1.5] Create a new content type that can tag content
• S3.4 [P1.5] UI to upload requirements file

Supporting documentation

<include links to technical docs, diagrams, etc>

Ready-Ready

https://docs.google.com/document/d/1dBW492UfCR5JxUvcx6efjYP_ibCdiwGONS-sxDb_SPU/edit# 

Complete Ready-Ready checklist

Definition of Done

Should be agreed upon per team; add/remove/update to reflect:{}

• CI is running, tests are automated and merged and successful
• DEV upstream code & tests merged
• DEV upstream documentation merged
• DEV downstream build attached to advisory
• QE - Test plans documented and attached to epic (or link to source)
• QE - automated tests merged and passing
• Docs - Downstream documentation is merged
• PM - all acceptance criteria are met (note: we want to start using the AC specific field, but please fill out below in the meantime)

Note: please also fill out the 'Acceptance Criteria' to indicate functional criteria aka scope, specific to this issue, that should be met in order to 'accept' the work to consider complete.