Security & Privacy FAQ page

A: Issue History for Jira is developed and maintained by SaaSJet, an Atlassian Platinum Marketplace Partner with enterprise customers worldwide.

A: Yes. Platinum Marketplace Partner status requires significant annual revenue, long-term ecosystem presence, and proven enterprise track record.

A: Yes. SaaSJet maintains SOC 2 Type II compliance and follows secure development lifecycle (SDLC) practices.

A: Licensing follows the Atlassian Marketplace subscription model based on user tier.

A: SaaSJet participates in the Marketplace Security Bug Bounty Program and follows responsible disclosure and remediation procedures.

A: Standard support is available during business hours, with enterprise-level coordination for security and procurement inquiries upon request.

A: Security-related inquiries are prioritized and handled by the dedicated security team.

A: Issue History for Jira does not store all customers' personal data in its databases; it only reads all changes "on the fly" in task logs and displays them in a convenient format. We only store the current add-on settings configuration, which specifies a set of rules on how to display changes.

A: The app stores:

• configuration of users' settings

• quick start template formats

• names of saved templates

A: We store service information in properties based on the Atlassian platform. What are properties? - Entity properties

A: We do not store personal information about our customers (names, addresses, emails, accounts). The rest of the service information is encrypted and transmitted using the TLS/SSL protocol and Encryption at rest.

A: Yes, the Issue History app does not save all changes in client tasks, it only reads the change log "on the fly" and shows the results of filtering in the add-on. Only the settings for working with the add-on can be saved.

Read our Privacy and Security Policy - https://saasjet.com/privacy-policy/

A: Issue History for Jira helps to meet such Part 11 FDA requirements:

• get an audit trail (log of all changes made to a file or data) to prevent falsified records

• track and keep deleted Jira issues to be sure nothing is lost forever

• export data from the system into a clear document (XLSX or CSV) to present it to FDA inspection

*There is no option for an electronic signature in the plugin.

Read more - How to get audit trail of changes to comply with 21 CFR Part 11Preview

A: You need to activate the option so that our app can receive information about the task deletion. We store information about a deleted task in Project properties AFTER it is deleted. What are Properties - see here Entity properties

Read more - Keep deleted work itemsPreview

A: The “Issue History” app has the option to keep deleted work items, which will help you to be held accountable for every deleted record. That would be extremely helpful when preparing for controls and audits. Here is detailed information on the current feature - Keep deleted work itemsPreview

A: Yes, we have a security officer in the company. Contact at security@saasjet.com

A: You can read the full list of our company's Policy by following this link - Documents are available upon the user's request.

• Amazon Cloudwatch

• Datadog

A: We work remotely according to the work schedule. Support center available (email and Jira requests) - 24/7, chat service from 12 pm to 8 pm (GMT+3), and phone service from 9 am to 12 am from Monday to Friday.

Our mission is to ensure information system uptime, data integrity, availability, and business continuity. We have process-level plans for recovering critical technology platforms and the telecommunications infrastructure in case of disaster. Learn more

A: Only the Lead responsible for the product and the DevOps engineer have access to production for quick response in case of an incident. All code is deployed automatically, and several specialists check each change.

A: Yes, Issue History for Jira app is Data Residency compliant. With Data Residency in Jira Cloud, you can control the geographic region where your data is stored.

More info - Data Residency in Issue History for JiraPreview

A: Yes, it is possible. According to the permissions section, you can add permissions at the group level to view changes, restore deleted work items, etc. For more information about this option, read here - Permissions for Working With Issue HistoryPreview

If you want to make access at the user level, you can create separate groups for the corresponding users.

A: Yes, we have backup / restore policy - Documents are available upon the user's request.

A: Yes, you can read more here - Documents are available upon the user's request.