# RP Epic Field Checklist

Standard page:
`https://reltio.jira.com/wiki/spaces/PM/pages/2688385025/PM+Standards+Epics`

Use this checklist during epic create/update.

## Core fields

- `Summary` (short Jira shorthand)
- `Description` (business outcome + impact)
- `Type of Effort`
- `Fix Version` (or `N/A` when not yet planned)
- `Status`

## Product narrative fields

- Problem Statement / Why
- Solution / What
- Persona / Who
- Value Statement

## Planning and delivery fields

- Confidence Level
- Path to Green (required when Confidence is Medium/Low for must-have epics)
- Availability in Release
- Planned Release
- T-Shirt Size
- Tier
- Initiative

## Ownership and dependencies

- Product Lead
- Engineering Lead
- UX Lead
- Execution Team
- Execution Team Dependency

## Go-to-market and governance

- For documentation tickets: set `Affected Documentation` to a documentation target (for example `Help Portal`) and never `No`
- Doc Required
- Pricing Required
- Security Review Required
- Does this change PCC?
- Tags (including `Must Have` when applicable)
- Demo Link (when available)

## Integration check

- `Aha! Reference` is present and linked through the RP integration path.