GitLab Learning & Development, 8 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab Jira Integration Differences

Description

Explanation of the difference between the basic GitLab Jira integration that's available in all editions and the Developer Panel that's only available in GitLab EE Premium and Ultimate.

A

Hi, I'm steve grossman a solution architect in the united states with git lab. Today, I'm going to share with you the differences between the basic gitlab integration with jira and the premium integration that's available with a premium or ultimate get lab enterprise edition subscription to level set. Let's review the basics of the gitlab integration with jira.

A

These integrations exist to mimic with jira the functionality we have built in with git lab issues.

A

There are two integrations: a basic integration, that's included with both community edition and enterprise edition at all, licensed tiers and a premium jira development panel integration that is available only with a premium or ultimate get lab enterprise subscription both integrations, allow for the creation of hyperlinks from gitlab commits and merge requests to a jira issue and navigation from the gillab object to jira and from gera to the gitlab object.

A

The differences between the integration are in how the links are presented to the user and how and when the links are created and how the integrations are set up. It's important to note that these integrations are not mutually exclusive premium and ultimate customers can have both integrations operational at the same time and most do now. Let's take a look at the differences between the two integrations.

A

The basic integration connects a gitlab project to an entire jira instance, where the premium integration connects one or more projects in a gitlab group to a single jira project. This provides much finer granularity when making links between the two tools and simplifies the user experience.

A

The premium integration allows links between gitlab branches commits and merge requests where the basic integration links only get lab, commits and merge requests.

A

The premium integration displays the links in the jira development panel, a side panel on the right side of the jira issue, view and consolidates the links by type such as a branch commits or pull requests.

A

The basic integration, on the other hand, shows the links as individual links in the same area as the issue comments, making the issue longer and viewing linked issues while leaving reading comments more difficult.

A

The setup of the premium integration is easy and well documented and is the same regardless of the get lab project or jira issue workflow. The basic integration relies on determining the jira transition ids, which are a numeric value that can differ between different jira projects.

A

These values, once obtained, can be templated in gitlab, so subsequent projects use the template, but this only works. If the subsequent jira project uses the same transition, ids the premium integration synchronizes, the links hourly or on demand for the basic integration creates the link immediately.

A

The difference is that, once a link is created in jira with the basic integration, it is never automatically updated. There is also a difference in how user authentication is handled.

A

Both integrations, enable jira, smart commits that allow jira issues to be transitioned or otherwise acted upon by keywords provided in the gitlab commit message.

A

Now, let's take a look at the differences in the user experience between the two integrations on the left side, we have a screenshot of the basic gear integration. As you can see, the links are in line in the issue and make it longer so more scrolling is required.

A

This also takes up precious vertical real estate on the screen and requires more scrolling to see all the comments on the right. We see the premium integration with the jira development panel. I've highlighted the panel with a red box for visibility.

A

As you can see, we have links to the branches which are not available with the basic integration, as well as links to the commits and pull requests rather than showing each link individually and making this page busy, for example, with multiple commits the premium integration consolidates those links under commits, so that clicking on the three commits link in the development panel will then show the links to the three individual commits thanks for watching. If this doesn't ask your questions answer your questions, ask them in the cs, questions internal slack, channel.