Security & Data Handling in Issue History for Jira

Your Jira work item data stays in Atlassian.

Issue History for Jira app works fully within the Atlassian infrastructure. It does not store Jira work item data externally, does not copy Jira history, and does not share Jira work item data with third parties.

🔐 Data Handling Overview

⚙️ Data Processing Model

💼 Enterprise Impact & Benefits

✔ Jira data stays within Atlassian infrastructure

✔ No external storage of Jira work item data

✔ No Jira data shared with third parties

✔ Built on Atlassian Forge

✔ Jira is the source of truth

✔ Data is read when needed via Atlassian APIs

✔ No separate storage of Jira data

✔ Processing happens within Atlassian Cloud

✔ No duplicated Jira data outside Atlassian

✔ No separate database for Jira data

✔ Easier security and compliance reviews

✔ Lower risk for enterprise teams

Built on Forge: Secure and compliant data processing

Issue History for Jira is built on Atlassian’s Forge platform, which means all data processing happens securely within the Atlassian cloud, not on external servers. This ensures your Jira work item data never leaves the trusted Atlassian infrastructure.

As a Forge-based app with the Runs on Atlassian badge, Issue History meets Atlassian’s highest standards for security, performance, and reliability.

⚙️Feature	🔌Atlassian Connect	☁️ Atlassian Forge (Issue History for Jira is built on it)
Hosting	App vendor’s external servers	Fully hosted on Atlassian infrastructure
Data security	Managed by vendor	Managed by Atlassian
Performance	Depends on vendor infrastructure	Optimized for Jira Cloud
Compliance	Varies by vendor	Easier compliance (SOC 2, ISO, etc.)
Future support	Still supported, but no new improvements	Atlassian’s main focus for new development

Questions & Answers

1. Does Issue History for Jira store customer data outside Atlassian?

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.

2. Does Issue History for Jira have its own database?

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

3. Does Issue History for Jira reside in Jira’s database?

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.

4. Is any customer data sent to third parties?

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

5. Is any Jira work item data stored outside the United States?

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.

6. What is your data residency model?

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.

7. What role does Datadog play in the system architecture?

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

8. Is Issue History for Jira a third-party app in Atlassian architecture?

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

9. What happens to data if the app is disabled or uninstalled?

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.

10. Can you summarize the architecture in simple terms?

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

If you need help or want to ask questions, please contact SaaSJet Support or email us at support@saasjet.atlassian.net

Have some additional questions? 👉 Book a product demo to review architecture, data flow, and compliance alignment with our team.