Check out Jira GitHub and GitLab Jira integration demo
All you need is to provide a server name, a repository name, a personal access token and give an alias. No additional settings are required. You can use limitation parameters to manage the frequency of server requests.
Add new branches easily, disable or remove abandoned repositories, and check the number of indexed commits. Here you can take a look at the status of repository server limitations. Tons of advanced configurations.
All issues, mentioned in a commit message or a pull request, are displayed on the Jigit tab page. Click on a commit link to look at the diff. Copy a commit id to the clipboard and share it with your teammates.
Move Work Forward is an independent Atlassian Marketplace Vendor. We do not have any affiliation with Atlassian.
Move Work Forward does not collect any data and we do not know how you use our products or what data is stored, so we rely on your feedback.
Jigit supports Jira Server and Data Center only.
Yes, you can schedule the video call here.
Move Work Forward provides a fully functional of Jigit for 30 days.
Once the trial period is over, the cost of the app will automatically be included in your next bill unless manually deactivated via the Manage Apps page under the Jira Administration menu. Evaluation licenses can be extended.
Data Center and Server: You can find the cost to purchase Microsoft Teams Jira Connector on your Jira Server instance here or your Jira Data Center here. Microsoft Teams Jira Connector for Server or Data Center is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price here.
You can use Jira GitHub & GitLab integration by Move Work Forward in 1 way:
Uni-directional. With the uni-directional way all data is stored in your Jira's database, and you use Incoming Webhook Connector in Microsoft Teams to receive notifications, alerts and reports in a particular Microsoft Teams channel directly from Jira. You cannot interact with those cards in Microsoft Teams, because data flows only one way from Jira to Microsoft Teams. This way is the most secure and provides you with more control over your data that sent outside. The messages are going from your Jira Server to Microsoft Teams servers directly.
You can find more information in our Security and Architecture guide.
Note: Jigit uses REST API of GitLab and GitHub to read the commit history without accessing the code. The App works via HTTP/S and does NOT clone the repositories.What data is stored?
You can find exact details in the Jigit Storage guide.
To revoke the access, you need to delete the rule in Jigit which is inrevertable, so be careful.
Microsoft Teams Jira Connector does not receive or store your credentials.
Definitely yes, you can use Microsoft Teams Jira Connector without being the Jira administrator. However, you may need some help from your Jira administrator to configure the application in some circumstances.
We usually reply within two business day, so please make sure our email has not hit your spam filters. If you haven't seen a reply within 48 hours or it is super urgent - please contact us at support at move work forward dot com.
We are humans who have families and hobbies, on top of this, we inspired to provide the best integration between Microsoft Teams and Jira, which requires time and effort to execute well. Notwithstanding these arguments, we s
Please use our Jira Service Portal (called F1) to submit a support request, feature request or just an enquiry. Do not forget to describe your problem in great details and attach the debug log if possible. We cannot guess about your issues.
At this stage, only Jira Server and Jira Data Center customers can extend their evaluation licenses. You can do this by completing this form and updating your product license under the "Manage Add-ons" page in the Admin panel.
Please contact us to discuss your requirements.
When purchasing an app license, the user tier must match that of Atlassian Jira. This is a requirement of the Atlassian Marketplace, as detailed in this Atlassian FAQ. Atlassian handles all licensing for Marketplace vendors so we can focus on what is important to us - providing quality software and supporting our customers. As a result, we are unable to modify the licensing to be restricted to specific user groups within a Jira instance.
All licensing matters are handled directly through Atlassian, so, unfortunately, there is nothing we can do as vendors to rectify this. Please reach out to email@example.com and open a ticket directly with Atlassian, they will be able to resolve this for you.
You can follow the the troubleshooting process defined in Jira GitHub & GitLab integration user guide.