Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×Hi everyone,
I’m working with the Jira Align Public API (v2) and ran into an issue when trying to filter Features (Epics) by Program/Sub-charter.
For active Features, the field primaryProgramId
(and additionalProgramIds
) works fine.
For recycled Features (isRecycled = 1
), the API response clears out primaryProgramId
(it comes back as null
).
This means I can’t filter or retrieve recycled Features by program ID. For Stories, the API does retain the program association even when recycled — but not for Features.
Example response for a recycled Feature:
{
"id": 55,
"title": "test epic soft delete",
"isRecycled": 1,
"primaryProgramId": null,
...
}
When I checked the audit log for that Feature (/features/{id}/auditlog
), I found the original “Epic Created” entry does include the program info, e.g.:
Primary Sub-Charter: 38: <obfuscated program name>
So technically the data is preserved in audit history, but that means I would need to fetch the audit log for every deleted Feature, which creates a lot of overhead.
Is there a supported way to retrieve the Program/Sub-charter mapping for recycled Features directly (without calling the audit log for each one)?
Are there any other endpoints in the public API that retain this mapping after deletion?
Would Enterprise Insights (EI) be the only reliable path for bulk/historical backfills?
Is this discrepancy between Stories and Features (program retained vs. null) a known limitation/bug?
Any guidance from others who have solved this — or from Atlassian staff — would be greatly appreciated 🙏