Skip to main content
Skip table of contents

Security Hub: SLA Time & Report

Certifications


Fortified.png

 

Cloud Fortified

The Cloud Fortified Apps Program aims to serve our largest customers and those with more business-critical operating requirements for apps.

 

BugBounty.png

 

Marketplace Security Bug Bounty Program

A bug bounty program is one of the most powerful post-production tools to help detect vulnerabilities in applications and services.

Frame-98.svg

 

Security Assessments

The term “security assessment” refers to any activity intended to determine, evaluate, or test the security features and controls of Atlassian’s products and services.

Premium-partner.svg

 

 

SaaSJet is a Platinum Marketplace Partner

What does “Platinum partner” mean? According to annual gross sales ("Purchase Price" in Marketplace reports), a minimum $1M annual gross sales comprised a minimum of 35% from the cloud.

Security


5ee82afd-96a8-4883-80ef-68914561c286.png

System and Organization Controls - SOC 2

SOC 2 reports are independent third-party examination reports demonstrating how an organization achieves key compliance controls and objectives.

  • What Atlassian says about Trust Service Criteria (TSC) - read more

  • SaaSJet is SOC 2 Type 2 compliant - read more

image-20240410-184007.png

 

CAIQ-Lite

CAIQ Lite is a simplified version of the Consensus Assessments Initiative Questionnaire (CAIQ), which is designed to assess the security posture of cloud service providers.

Atlassian requires all Platinum, Gold, and Silver Marketplace Partners to complete the CAIQ-Lite questionnaire, which it then reviews.

  • What Atlassian says about the security of the cloud ecosystem - read more

 

security-contact.png

 

Security Contact

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please contact us at security@saasjet.com

Support


 

help.png

 

Working hours: Mon-Fri 24hrs GMT+3

Phone: +1 888 396 0501

Book a demo session: click to schedule an online free demo

Support portal: click to create a ticket

Help: Read the documentation


We understand that data security is of utmost importance to our users. The information below outlines the types of data stored by SLA Time and Report for Jira, associated security measures, and storage periods, addressing your data privacy concerns.

Data storage


  • Data Stored in our MongoDB Database

    • SLA Configuration: We store the structure of your SLA configurations, including project type, field type, field name, and configuration settings. This information is required to ensure the correct calculation and visualization of SLA metrics within Jira.

    • User ID: We associate a unique User ID with SLA configurations and reports to support internal tracking and management within our system. This helps ensure secure, accurate processing without storing any personal data.

  • Data Stored within Jira

    • Task-Related Submissions: Notifications and SLA events that you configure in the app are sent directly to Jira issues and stored within the Jira environment. All SLA timers, statuses, and notifications visible in issues are handled and retained inside Jira, not in external databases.

Important Note: We do NOT store personal user data such as emails or names while you are using our applications. We can store your personal information in 2 cases:

  •  to respond to your direct request if you contact us for support.

  •  if your name and email are specified as your organization’s billing or technical contact during the subscription process.

We do not collect this information independently. We see only the information you have specified.

Data Retention Period


  • App Information: (Text, Atlassian ID) Stored until you or an authorized user deletes it.

  • Deactivated/Terminated Accounts: Data remains accessible for team members/users until no longer needed.

  • Uninstalled App: By default, your SLA data is retained for 90 days to allow for subscription renewal. After this period, all data is automatically deleted.

Data Security


Your data is protected through multiple layers of security:

  • Encryption: Protecting your data in transit.

  • Strict Access Controls: Limiting database access to authorized personnel only.

  • System Updates and Monitoring: Keeping everything up-to-date and secure against potential issues.

App internal restrictions


Access to SLA Time and Report functionality is managed through group-based permissions within Jira.

  • Access to app pages (SLA Manager, Permissions, and Reports) can be individually granted by administrators to specific user groups.

  • The SLA widget in Jira issue panels is visible to all users who have access to that issue.

  • When creating or sharing JQL-based views in SLA Manager or Reports, please note that any information included in the JQL query (such as project name, project key, or field values) will be visible to users who have access to that shared view. If a view is made public, its JQL query becomes visible to all users with access to the app.nTherefore, we recommend avoiding the inclusion of sensitive or confidential project identifiers in JQL expressions that are intended to be shared publicly.

  • The widget will not appear in projects where no SLA configuration has been linked.

This approach ensures granular control and visibility aligned with your team’s permissions model.

Changes to Policy


Any significant changes that occur in our data security and retention practices will be communicated on our website.

Read about the SaaSJet Privacy Policy ->


If you need help or want to ask questions, please get in touch with us through SaaSJet Support (Time of the First Response ≤ 4 hours) or via email at support@saasjet.atlassian.net

Haven't used this add-on yet, then try it now!

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.