Based on the codebase, this is not possible in DefectDojo v2.53.3 (or any current version).
Here's why:
How EPIC linking works today:
When you push an engagement to Jira, DefectDojo creates a JIRA_Issue record linked to that engagement via a OneToOneField
This is a hard one-to-one relationship: each engagement gets its own, unique EPIC — sharing is not supported at the database or application level
What you're asking for isn't supported:
There's no UI field to enter an existing EPIC key for an engagement
There's no way to point multiple engagements at the same Jira EPIC
The push_to_jira form for engagements only lets you set epic_name and epic_priority — it always creates a new EPIC (or updates the one it already owns)
Workarounds to consider:
- 1.
Use the same Jira EPIC manually outside DefectDojo — link findings from engagements 2 & 3 to the EPIC manually in Jira itself. DefectDojo won't know about this link but findings can still be pushed as Jira issues.
- 2.
Use one engagement instead of three — if the scope is really under one EPIC, consider consolidating the work into a single engagement with multiple tests/test types.
- 3.
Jira automation rules — in Jira, set up an automation rule that automatically links issues from engagements 2 & 3 to the EPIC from engagement 1, based on a label or project.
- 4.
Feature request — this would need a code change to add an "existing EPIC key" field to the engagement Jira form and remove the OneToOneField constraint. You could open a GitHub issue requesting it.
