Check all Jira IDs in the tickets.yaml to ensure that they point to SAT features or epics, not to RN trackers or doc tasks.

Update: The Sat docs team wants to track doc issues with aCoRNs.

We can address this issue by using the aCoRNs "reference" function in the tickets.yml:

- [Jira, key: DOCS-1234, { references: [[Jira, key: FEATURE-5678]}]

Result: "DOCS-1234, FEATURE-5678".

Only publicly visible issues are hyperlinked. If we ensure that the doc tracker security is "RH only", aCoRNs does not generate a hyperlink.

I recommend adding a reference Jira even for features that are not public because the feature issue ID can be used internally.

Alternatively, we could create the reference structure with the feature issue ID commented out, and then uncomment the feature and comment out the tracker just before release:

- [Jira, key: DOCS-1234, { references: [[Jira, key: FEATURE-5678]}]
# - [Jira, key: FEATURE-5678]