Frequently Asked Questions

Linking is done automatically via issue or task identifiers. For Jira, include an issue key (e.g. ABC-123) in your Git commit message, branch name, or pull request title. For monday.com, include the task ID. Each commit, branch, and pull request can be linked to multiple issues. Check out our documentation for comprehensive information.

We host our applications at Microsoft Azure, with servers located in the United Kingdom.

We understand that keeping source code secure is a matter of utmost importance, and we have introduced various measures to ensure your code is safe:

• We do not store your source code on our servers. We only store the metadata that is needed to link issues to your code — namely commit messages, branch names, pull request titles, and repository URLs.
• All communication between our plugins, your Git repositories, and Jira or monday.com is performed securely via HTTPS.
• The access tokens required to access your Git repositories are stored in an encrypted form.
• You have full control of your access tokens through your account at GitHub, GitLab, Azure, or AWS. Should you decide that you no longer want to share your Git data, you can simply deactivate the access token and our plugins will be unable to access your repositories.
• All our products are hosted at Microsoft Azure which offers a very high level of security, and advanced tools for auditing and detecting security incidents.
• When you uninstall one of our plugins, your data may be kept for a maximum of 30 days. After that, it is permanently deleted and becomes inaccessible for anyone. If you want your data to be deleted instantly, just contact us and we will do that for you.

If your Git repositories are hosted on-premise behind a firewall, you will need to allow inbound connections from our servers. Our plugins use the following outbound IP addresses:

3.8.173.227
51.143.228.209
51.143.229.5
51.143.229.29
51.143.229.38
51.143.229.71
51.143.229.203
51.104.28.72
4.158.117.10
51.143.229.226
51.143.230.17
51.143.230.55
51.143.230.73
51.143.225.143
51.143.230.106
51.143.230.114
51.143.230.140
51.143.230.218
51.143.230.228
51.143.230.242
51.143.230.244
51.143.230.253
51.143.231.30
51.143.231.50
51.143.231.144
51.143.231.159
51.143.231.231
20.77.184.4
20.49.137.113
20.77.184.11
20.77.184.28
20.77.184.51
20.77.184.57
51.11.47.121
51.11.47.178
51.132.168.104
51.132.169.245
51.132.170.120
51.132.171.18
20.90.192.143
20.108.107.17
20.26.137.101
20.26.138.141
20.26.138.187
20.26.138.243
20.90.134.31
20.26.139.127
20.108.198.120
20.26.139.170
20.26.140.72
20.26.140.151
20.26.140.165
20.26.140.167
20.26.140.197
20.26.141.240
20.26.142.113
20.26.142.183
20.26.142.189
20.26.143.82
20.26.143.110
20.26.143.136
20.26.143.179
4.234.40.78
4.234.40.171

Please ensure all of these IP addresses are allowed through your firewall. This list may change over time — we recommend checking this page periodically or contacting us to be notified of any changes.

Our plugins only store the metadata needed to link your issues and tasks to Git data (commit messages, branch names, pull request titles, and repository URLs). We do not store your source code.

Access tokens used to connect to your Git repositories are encrypted at rest using AES-256 encryption.

Yes. We take a multi-layered approach to security testing:

• Our apps are periodically tested by external parties as part of Atlassian's Bug Bounty program.
• We run automatic penetration testing on all public-facing infrastructure, including via Atlassian's Ecoscanner platform which performs regular security checks across all our Marketplace apps.
• We use automatic security source code analysis tools to detect potentially vulnerable areas of code before they reach production.
• We perform regular cyber-security health checks on our servers and development machines to detect common security misconfigurations and inadequate access controls.

We have a zero tolerance policy for security vulnerabilities. If a vulnerability is discovered or reported, we prioritize fixing it above all other work. Regardless of severity, fixes are applied as soon as they are ready — typically within 24 hours.

We adhere to Atlassian's Security Bug Fix Policy and report any security incidents through Atlassian's App Security Incident workflow. If customer data is affected, we communicate directly with affected customers via email and/or release notes.

Yes. All our infrastructure is hosted on Microsoft Azure with the following recovery and redundancy mechanisms:

• Azure Site Recovery — automatically replicates workloads to secondary locations.
• Azure Backup — backs up all servers every hour, and offers point-in-time restore for databases.
• Automatic re-sync — most stored data is synced from your Git repositories. In the event of data loss on our servers, it is automatically re-synced from your Git provider, typically within minutes to 2 hours. There is no permanent data loss.

We also maintain clear documentation for handling various types of service outages, and all team members work remotely, eliminating risks of physical disasters affecting office infrastructure.

Reach out to us, and we will be happy to answer any remaining questions.