Security & Data Handling in Issue History for Jira

No. Issue History for Jira doesn’t store Jira work item data, history, or content in its own external database.

All Jira work item data is:

• Processed inside Atlassian Cloud infrastructure

• Not copied, persisted, or mirrored outside Atlassian systems

Issue History for Jira app can read the full task log "on the fly,” parse the data, format it, and show it to the user.

Open

No. Issue History for Jira doesn't maintain a separate customer data database.

The app:

• Doesn't pull full work item histories into an external DB

• Doesn't store work item fields, comments, or change history outside Jira

• Uses Atlassian-provided Forge storage only for minimal operational metadata, not customer work item data

Issue History for Jira app:

• Reads data from Jira at runtime

• Processes it within Atlassian Cloud

• Doesn't write customer work item data back into Jira databases

• Doesn't persist work item data elsewhere

The source of truth for all work item data remains Jira itself.

No Jira work item data is sent to third parties.

The app uses limited third-party services only for operational purposes, such as:

• App monitoring and error logging

• Performance metrics

These services:

• Don't receive Jira work item content

• Don't receive change history

• Don't receive customer business data

No. Issue History for Jira follows Atlassian Cloud data residency rules.

Customer Jira data:

• Remains in the Atlassian Cloud region selected by the customer

• Isn't moved, copied, or stored by Issue History for Jira app outside that region

Issue History for Jira app is Data Residency compliant.

Open

Issue History for Jira:

• Inherits Atlassian Cloud data residency

• Doesn't define or require its own data residency

• Doesn't move data between regions

If your Jira instance is hosted in the US, EU, or another supported region, your data stays there.

Datadog is used only for app monitoring, such as:

• System health

• Error tracking

• Performance insights

Important clarifications:

• No Jira work item data is sent to Datadog

• No customer content is processed by Datadog

• Monitoring data doesn't include business or personal data

Yes. Issue History for Jira is a third-party Atlassian Marketplace app, built on Forge (Runs on Atlassian).

This means:

• The app runs inside Atlassian’s infrastructure

• It follows Atlassian security, isolation, and permission models

• It doesn't run its own servers

If Issue History for Jira is disabled or uninstalled:

• No Jira work item data is deleted or changed

• Jira remains the system of record

• No historical Jira data is lost

The app doesn't “own” or persist Jira work item data.

Yes, simply put:

• Jira stores all work item data

• Issue History for Jira reads data securely via Atlassian APIs

• Processing happens inside Atlassian Cloud

• No work item data is stored externally

• No work item data is sent to third parties