Connecting Jira SD to Gitlab

[LP]

Hello,

I am new to Jira.

The situation: We are a small business with a 3-man service desk and an external developer. We are using Jira. The Developer is using Gitlab. They would NOT move to Bitbucket.

What I'd Like to Do: Transfer tickets (CRs, Incidents, Problems) to the Gitlab instance the dev team is using, see their updates. I.e. See in Jira what's going on in Gitlab.

Is this possible? If so,

could someone point me to the documentation and other helpful resources?

Much obliged.

lp

[Andy Heinzer · Accepted solution]

Hi LP,

I see that you are wanting to integration Jira Cloud with Gitlab.  Unfortunately, Jira Cloud natively does not yet support this provider.  That said this at least one app in the Marketplace that can help here.  Check out the GitLab.com for Jira Cloud app. 

This might not be able to handle all of the asks here though.  This integration does not really let you transfer Jira issues to Gitlab, but this can then provide Jira Cloud with a very similar integration that are possible natively to Bitbucket, or much like the github app can do for that service.  When git events such as pull requests, commits, branches includes messages that directly reference a specific Jira issue key, Jira can let you see some more details about those pull requests, code, etc.

Does this help?  Or are you specifically looking for some means of taking Jira issue data and sending it to Gitlab in some manner?  

If you're looking for that kind of functionality, I would have to learn some more about how Gitlab might allow you to create issues there.  I'm not well versed on using that particular product.  But that said, Jira Cloud sites all now have automation as a feature.  The automation in Jira Cloud can let you setup rules that could send a webhook.  If Gitlab can be configured to create issues from incoming webhooks, then you might be able to setup Jira to send that data to this other application.  More automation overview in Automate your Jira Cloud processes and workflows.

Let me know what you think.

Andy

[LP]

Hi Andy,

thank you for your thoughtful reply.

The only functionality I have is for Incident and CR updates sent to GL. I don't care for the inner workings of the dev team, from a Service Desk perspective. I only care for comment updates and SLA data. Comments should go both ways, though.

We have decided to go with Jira SD, even if it doesn't integrate with GL. I would hate double data entry, because it would not provide the KPIs I need.

I will put to the dev team the solution you suggested.

Many thanks, again, lp