--- title: "Jira connector: setup and compatibility | Stacksync" description: "Jira integration guide: plan Issues and Projects, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/jira last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # Jira integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Jira workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Issues, Projects and Users. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Issues** - **Projects** - **Comments** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=jira) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Jira records to discuss. These Jira record examples help scope a technical review. They are not a list of verified Stacksync operations. Issues Use a stable task/work-item ID and preserve its project or parent-ticket reference. Projects Keep the project ID and organization/workspace context; a project title is not a stable key. Comments Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Worklogs Identify this record type and the operation you need to review with Stacksync. Sprints Identify this record type and the operation you need to review with Stacksync. Versions Identify this record type and the operation you need to review with Stacksync. Connection setup ## Jira connection requirements. Review Jira access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Jira account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Jira, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Jira integration. Choose how projects, work items, users, and milestones relate across systems. Agree on status transitions and which system may reopen or complete work. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Jira **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Use a stable task/work-item ID and preserve its project or parent-ticket reference. Load related records in the right order Resolve project, user, and parent-item references before the task. ### Mapping checks by record type #### Issues Confirm object support with Stacksync Identity Use a stable task/work-item ID and preserve its project or parent-ticket reference. Fields to consider Source task ID · Parent reference · Assignee · Status · Due date Related records to resolve first Resolve project, user, and parent-item references before the task. Test before going live Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. #### Projects Confirm object support with Stacksync Identity Keep the project ID and organization/workspace context; a project title is not a stable key. Fields to consider Source project ID · Workspace reference · Name · Owner · Lifecycle status Related records to resolve first Resolve workspace, owner, and any customer or budget references. Test before going live Test duplicate project names in different workspaces and an archived project with open tasks. #### Users Confirm object support with Stacksync Identity Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Fields to consider Source user ID · Tenant reference · Account status · Group references Related records to resolve first Resolve tenant and group references and establish a protected administrative-account policy. Test before going live Test a renamed login, disabled account, missing group, and a user existing in two tenants. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Jira integration in four steps. A reassigned work item retains its parent; a repeated status change does not reopen completed work or create a duplicate task. ### View the four setup tests and expected results 1. ### Confirm the intended Jira account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Issues Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. **Expected result:** A reassigned work item retains its parent; a repeated status change does not reopen completed work or create a duplicate task. 3. ### Test the operation your workflow needs Review one Jira record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Jira integration. ### Diagnose record matching, delayed changes, and rejected operations A Jira record appears under the wrong destination record Use a stable task/work-item ID and preserve its project or parent-ticket reference. Resolve project, user, and parent-item references before the task. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Jira implementation’s change-detection method for Issues, Projects and Users. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Jira object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Jira workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=jira) ## Jira integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) - [article Your Commits Reach Jira. Your Issues Stay Behind.](https://www.stacksync.com/blog/sync-github-with-jira) FAQ ## Jira connector FAQ ### How should I plan an integration with Jira? Choose how projects, work items, users, and milestones relate across systems. Agree on status transitions and which system may reopen or complete work. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Jira connector write changes back? Write-back support is not established for this connection. Review the Jira records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Jira data? Use a stable task/work-item ID and preserve its project or parent-ticket reference. ### Which related records should I load first for Jira? Resolve project, user, and parent-item references before the task. ### How do I validate Jira changes after the initial load? Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. A reassigned work item retains its parent; a repeated status change does not reopen completed work or create a duplicate task. ### What will we cover in a Jira integration demo? Start with one workflow and a sample record from Issues, Projects and Users. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Jira from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Jira and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Jira. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Jira record changes.” - “Create a Genie that answers questions about our Jira data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Jira connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Jira and Slack](https://www.stacksync.com/integrations/jira-and-slack) - [Jira and Smartsheet](https://www.stacksync.com/integrations/jira-and-smartsheet) - [GitHub and Jira](https://www.stacksync.com/integrations/github-and-jira) - [Jira and SharePoint](https://www.stacksync.com/integrations/jira-and-sharepoint) - [Jira and ServiceNow](https://www.stacksync.com/integrations/jira-and-servicenow) - [Google Sheets and Jira](https://www.stacksync.com/integrations/google-sheets-and-jira) - [Jira and Zendesk](https://www.stacksync.com/integrations/jira-and-zendesk) - [Jira and Notion](https://www.stacksync.com/integrations/jira-and-notion) ### Database · 50 - [Jira and Airtable](https://www.stacksync.com/integrations/airtable-and-jira) - [Jira and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-jira) - [Jira and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-jira) - [Jira and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-jira) - [Jira and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-jira) - [Jira and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-jira) - [Jira and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-jira) - [Jira and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-jira) - [Jira and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-jira) - [Jira and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-jira) - [Jira and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-jira) - [Jira and Citus](https://www.stacksync.com/integrations/citus-and-jira) - [Jira and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-jira) - [Jira and Couchbase](https://www.stacksync.com/integrations/couchbase-and-jira) - [Jira and DuckDB](https://www.stacksync.com/integrations/duckdb-and-jira) - [Jira and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-jira) - [Jira and Firebase](https://www.stacksync.com/integrations/firebase-and-jira) - [Jira and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-jira) - [Jira and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-jira) - [Jira and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-jira) - [Jira and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-jira) - [Jira and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-jira) - [Jira and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-jira) - [Jira and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-jira) - [Jira and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-jira) - [Jira and JDBC](https://www.stacksync.com/integrations/jdbc-and-jira) - [Jira and MariaDB](https://www.stacksync.com/integrations/jira-and-mariadb) - [Jira and MarkLogic](https://www.stacksync.com/integrations/jira-and-marklogic) - [Jira and MongoDB](https://www.stacksync.com/integrations/jira-and-mongodb) - [Jira and MySQL](https://www.stacksync.com/integrations/jira-and-mysql) - [Jira and Neo4j](https://www.stacksync.com/integrations/jira-and-neo4j) - [Jira and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/jira-and-oci-database) - [Jira and OpenSearch](https://www.stacksync.com/integrations/jira-and-opensearch) - [Jira and Oracle DB](https://www.stacksync.com/integrations/jira-and-oracle-db) - [Jira and Postgres Heroku](https://www.stacksync.com/integrations/jira-and-postgres-heroku) - [Jira and PostgreSQL](https://www.stacksync.com/integrations/jira-and-postgresql) - [Jira and RavenDB](https://www.stacksync.com/integrations/jira-and-ravendb) - [Jira and Redis Enterprise](https://www.stacksync.com/integrations/jira-and-redis-enterprise) - [Jira and Reltio](https://www.stacksync.com/integrations/jira-and-reltio) - [Jira and Render Postgres](https://www.stacksync.com/integrations/jira-and-render-postgres) - [Jira and SAP ASE (Sybase)](https://www.stacksync.com/integrations/jira-and-sap-ase-sybase) - [Jira and SAP HANA](https://www.stacksync.com/integrations/jira-and-sap-hana) - [Jira and Scaleway Postgres](https://www.stacksync.com/integrations/jira-and-scaleway-postgres) - [Jira and SingleStore](https://www.stacksync.com/integrations/jira-and-singlestore) - [Jira and SQL Server](https://www.stacksync.com/integrations/jira-and-sql-server) - [Jira and Supabase](https://www.stacksync.com/integrations/jira-and-supabase) - [Jira and TiDB](https://www.stacksync.com/integrations/jira-and-tidb) - [Jira and TimescaleDB](https://www.stacksync.com/integrations/jira-and-timescaledb) - [Jira and VoltDB](https://www.stacksync.com/integrations/jira-and-voltdb) - [Jira and YugabyteDB](https://www.stacksync.com/integrations/jira-and-yugabytedb) ### Data warehouse · 28 - [Jira and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-jira) - [Jira and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-jira) - [Jira and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-jira) - [Jira and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-jira) - [Jira and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-jira) - [Jira and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-jira) - [Jira and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-jira) - [Jira and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-jira) - [Jira and BigQuery](https://www.stacksync.com/integrations/bigquery-and-jira) - [Jira and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-jira) - [Jira and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-jira) - [Jira and Databricks](https://www.stacksync.com/integrations/databricks-and-jira) - [Jira and Dremio](https://www.stacksync.com/integrations/dremio-and-jira) - [Jira and Exasol](https://www.stacksync.com/integrations/exasol-and-jira) - [Jira and Firebolt](https://www.stacksync.com/integrations/firebolt-and-jira) - [Jira and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-jira) - [Jira and Greenplum](https://www.stacksync.com/integrations/greenplum-and-jira) - [Jira and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-jira) - [Jira and Materialize](https://www.stacksync.com/integrations/jira-and-materialize) - [Jira and MotherDuck](https://www.stacksync.com/integrations/jira-and-motherduck) - [Jira and Rockset](https://www.stacksync.com/integrations/jira-and-rockset) - [Jira and Snowflake](https://www.stacksync.com/integrations/jira-and-snowflake) - [Jira and Starburst Enterprise](https://www.stacksync.com/integrations/jira-and-starburst-enterprise) - [Jira and StarRocks](https://www.stacksync.com/integrations/jira-and-starrocks) - [Jira and Teradata Vantage](https://www.stacksync.com/integrations/jira-and-teradata-vantage) - [Jira and Tinybird](https://www.stacksync.com/integrations/jira-and-tinybird) - [Jira and Vertica](https://www.stacksync.com/integrations/jira-and-vertica) - [Jira and Yellowbrick](https://www.stacksync.com/integrations/jira-and-yellowbrick) ### Business productivity · 37 - [Jira and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-jira) - [Jira and Agiloft](https://www.stacksync.com/integrations/agiloft-and-jira) - [Jira and Asana](https://www.stacksync.com/integrations/asana-and-jira) - [Jira and Atlassian](https://www.stacksync.com/integrations/atlassian-and-jira) - [Jira and Braze](https://www.stacksync.com/integrations/braze-and-jira) - [Jira and Campfire](https://www.stacksync.com/integrations/campfire-and-jira) - [Jira and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-jira) - [Jira and Customer.io](https://www.stacksync.com/integrations/customer-io-and-jira) - [Jira and Docusign](https://www.stacksync.com/integrations/docusign-and-jira) - [Jira and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-jira) - [Jira and Front](https://www.stacksync.com/integrations/front-and-jira) - [Jira and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-jira) - [Jira and Gainsight](https://www.stacksync.com/integrations/gainsight-and-jira) - [Jira and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-jira) - [Jira and GitHub](https://www.stacksync.com/integrations/github-and-jira) - [Jira and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-jira) - [Jira and Ironclad](https://www.stacksync.com/integrations/ironclad-and-jira) - [Jira and Klaviyo](https://www.stacksync.com/integrations/jira-and-klaviyo) - [Jira and Lemlist](https://www.stacksync.com/integrations/jira-and-lemlist) - [Jira and Microsoft 365](https://www.stacksync.com/integrations/jira-and-microsoft-365) - [Jira and Microsoft Dynamics 365](https://www.stacksync.com/integrations/jira-and-microsoft-dynamics-365) - [Jira and Microsoft Teams](https://www.stacksync.com/integrations/jira-and-microsoft-teams) - [Jira and Monday](https://www.stacksync.com/integrations/jira-and-monday) - [Jira and NextGen Healthcare](https://www.stacksync.com/integrations/jira-and-nextgen-healthcare) - [Jira and Notion](https://www.stacksync.com/integrations/jira-and-notion) - [Jira and Orderful](https://www.stacksync.com/integrations/jira-and-orderful) - [Jira and Quip](https://www.stacksync.com/integrations/jira-and-quip) - [Jira and Resend](https://www.stacksync.com/integrations/jira-and-resend) - [Jira and SendGrid](https://www.stacksync.com/integrations/jira-and-sendgrid) - [Jira and ServiceMax](https://www.stacksync.com/integrations/jira-and-servicemax) - [Jira and ServiceNow](https://www.stacksync.com/integrations/jira-and-servicenow) - [Jira and Slack](https://www.stacksync.com/integrations/jira-and-slack) - [Jira and Smartsheet](https://www.stacksync.com/integrations/jira-and-smartsheet) - [Jira and SysAid](https://www.stacksync.com/integrations/jira-and-sysaid) - [Jira and Twilio](https://www.stacksync.com/integrations/jira-and-twilio) - [Jira and Wrike](https://www.stacksync.com/integrations/jira-and-wrike) - [Jira and Zendesk](https://www.stacksync.com/integrations/jira-and-zendesk) ### Analytics · 3 - [Jira and Pendo](https://www.stacksync.com/integrations/jira-and-pendo) - [Jira and Splunk](https://www.stacksync.com/integrations/jira-and-splunk) - [Jira and Treasure Data](https://www.stacksync.com/integrations/jira-and-treasuredata) ### Communications · 5 - [Jira and Aircall](https://www.stacksync.com/integrations/aircall-and-jira) - [Jira and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-jira) - [Jira and Infobip](https://www.stacksync.com/integrations/infobip-and-jira) - [Jira and RingCentral](https://www.stacksync.com/integrations/jira-and-ringcentral) - [Jira and Zoom](https://www.stacksync.com/integrations/jira-and-zoom) ### Security and identity · 6 - [Jira and Active Directory](https://www.stacksync.com/integrations/active-directory-and-jira) - [Jira and Auth0](https://www.stacksync.com/integrations/auth0-and-jira) - [Jira and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-jira) - [Jira and JumpCloud](https://www.stacksync.com/integrations/jira-and-jumpcloud) - [Jira and Okta](https://www.stacksync.com/integrations/jira-and-okta) - [Jira and OneLogin](https://www.stacksync.com/integrations/jira-and-onelogin) ### Storage · 4 - [Jira and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-jira) - [Jira and Box](https://www.stacksync.com/integrations/box-and-jira) - [Jira and Egnyte](https://www.stacksync.com/integrations/egnyte-and-jira) - [Jira and SharePoint](https://www.stacksync.com/integrations/jira-and-sharepoint) SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)