Here you can find the answers to some frequently asked questions about Azure Git Listener for Jira
What is Azure Git Listener?
Azure Git Listener is a plugin for Atlassian Jira Cloud that links your Jira to Azure Git repositories. It adds a "Azure Git" section to each issue page, that displays all Git commits, branches, and pull requests linked to the current Jira issue.
How is Git data linked to Jira issues?
Linking is done via Jira issue keys, which are always in the following form: ABC-123. Just include an issue key in you Git commit message, branch name, or pull request title, and it will be displayed by Azure Git Listener on the corresponding issue's page. Each commit, branch, and pull request can be linked to multiple Jira issues. Check out our documentation for comprehensive information.
Do you support Jira Server?
Currently we don't, but we have plans to introduce this support. Reach out to us if you want to be notified when this happens.
Where does Azure Git Listener store my information?
We host our applications at Microsoft Azure, with servers located in the United Kingdom.
How secure is Azure Git Listener?
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 Jira tickets to your code. Namely, this data is commit messages, branch names, pull request titles, and the URLs of your Git repositories.
-
All communication between Azure Git Listener, Git repositories, and Jira is performed securely via HTTPS.
-
The access tokens that Azure Git Listener requires to access your Git repositories are stored in an encrypted form.
-
You have full control of your access tokens through Azure DevOps portal. Should you decide that you do not want to share your Git data with Azure Git Listener, you can just deactivate the access token, and Azure Git Listener will be unable to access your code any more.
-
Azure Git Listener is hosted at Microsoft Azure which offers a very high level of security, and advanced tools for auditing and detecting security incidents.
-
When you uninstall Azure Git Listener from your Jira instance, 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.
Still have questions?
Reach out to us, and we will be happy to answer any remaining questions.
What is GitLab Listener?
GitLab Listener is a plugin for Atlassian Jira Cloud that links your Jira to GitLab repositories. It adds a "GitLab" section to each issue page, that displays all Git commits, branches, and pull requests linked to the current Jira issue.
How is Git data linked to Jira issues?
Linking is done via Jira issue keys, which are always in the following form: ABC-123. Just include an issue key in you Git commit message, branch name, or pull request title, and it will be displayed by GitLab Listener on the corresponding issue's page. Each commit, branch, and pull request can be linked to multiple Jira issues. Check out our documentation for comprehensive information.
Do you support Jira Server?
No, we do not support Jira Server.
Where does GitLab Listener store my information?
We host our applications at Microsoft Azure, with servers located in the United Kingdom.
How secure is GitLab Listener?
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 Jira tickets to your code. Namely, this data is commit messages, branch names, pull request titles, and the URLs of your Git repositories.
-
All communication between GitLab Listener, Git repositories, and Jira is performed securely via HTTPS.
-
The access tokens that GitLab Listener requires to access your Git repositories are stored in an encrypted form.
-
You have full control of your access tokens through your GitLab account. Should you decide that you do not want to share your Git data with GitLab Listener, you can just deactivate the access token, and GitLab Listener will be unable to access your code any more.
-
GitLab Listener is hosted at Microsoft Azure which offers a very high level of security, and advanced tools for auditing and detecting security incidents.
-
When you uninstall GitLab Listener from your Jira instance, 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.
Still have questions?
Reach out to us, and we will be happy to answer any remaining questions.
What is AWS CodeCommit Git Listener?
AWS CodeCommit Git Listener is a plugin for Atlassian Jira Cloud that links your Jira to AWS CodeCommit Git repositories. It adds a "CodeCommit Git" section to each issue page, that displays all Git commits, branches, and pull requests linked to the current Jira issue.
How is Git data linked to Jira issues?
Linking is done via Jira issue keys, which are always in the following form: ABC-123. Just include an issue key in you Git commit message, branch name, or pull request title, and it will be displayed by AWS CodeCommit Git Listener on the corresponding issue's page. Each commit, branch, and pull request can be linked to multiple Jira issues. Check out our documentation for comprehensive information.
Do you support Jira Server?
No, we do not support Jira Server.
Where does AWS CodeCommit Git Listener store my information?
We host our applications at Microsoft Azure, with servers located in the United Kingdom.
How secure is AWS CodeCommit Git Listener?
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 Jira tickets to your code. Namely, this data is commit messages, branch names, pull request titles, and the URLs of your Git repositories.
-
All communication between AWS CodeCommit Git Listener, Git repositories, and Jira is performed securely via HTTPS.
-
The access tokens that AWS CodeCommit Git Listener requires to access your Git repositories are stored in an encrypted form.
-
You have full control of your access tokens through AWS console. Should you decide that you do not want to share your Git data with AWS CodeCommit Git Listener, you can just deactivate the access token, and AWS CodeCommit Git Listener will be unable to access your code any more.
-
AWS CodeCommit Git Listener is hosted at Microsoft Azure which offers a very high level of security, and advanced tools for auditing and detecting security incidents.
-
When you uninstall AWS CodeCommit Git Listener from your Jira instance, 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.
Still have questions?
Reach out to us, and we will be happy to answer any remaining questions.