Tab page. This is how to browse issue commits. Links lead to diff pages at Git server side.
Add new repository dialog. Less parameters, more profit.
Config page.Add new branches, disable or remove abandoned repositories, check number of indexed commits.
I wanted to integrate a GitLab server with JIRA without cloning a repo, because it's very inconvenient. I started to read the documentation and found that a lot of Git servers have public HTTP API. So, I decided to use this way of integration.
What it does
All you need to start using it is to provide a server name, a repository name and a personal access token. No additional settings are required. Then, the add-on interrogates servers using their API and saves commits in a JIRA database. The add-on provides an issue tab, which displays information about all commits referencing to the issue key.
Challenges I ran into
I had to minimise system requirements, that is why I have implemented my own lightweight clients for GitHub and GitLab. All known java clients demand too much memory because they cover all cases.
Accomplishments that I'm proud of
I have developed and published a useful add-on. It is great to read rave reviews from users.
What's next for Jigit - GitHub and GitLab integration
I am going to support the add-on and to develop its features.