Summary

There is a discrepancy between how Jira handles project archiving and how that data is represented in the Atlassian Data Lake.

In Jira, archiving a project (or space) is a comprehensive action. As per Atlassian documentation:

"The space along with its work items, Jira components, attachments, and versions will be archived. Work items will be read-only and can be accessed via a direct link. Archived spaces won’t appear in directories and their work items won’t appear in search."

However, in Atlassian Analytics, this and "archived" state does not automatically propagate to the work items. While jira_project.status updates to 'archived', the jira_issue.is_archived boolean remains false. This means that unless a user manually adds a second filter for project status, "archived" issues continue to appear in Analytics charts and reports, contrary to their behaviour in the Jira UI.

Suggested Solutions

Align the Data Lake logic with Jira's UI behaviour. If a project is archived, all child work items should automatically return is_archived = true in the jira_issue table.

This should also apply for the following the future as well:

• Jira components, attachments, and versions will be archived

Suggested Workarounds

Users currently need to apply a dual-filter strategy in all queries and charts to ensure a clean dataset:

1. jira_project.status = 'active' (to exclude issues from archived projects/spaces).
2. jira_issue.is_archived = false (to exclude individually archived issues).