Customers have installed this app in at least 692 active instances.
    by Allenta Consulting S.L. (CIF ESB15974553)for JIRA Server 7.0.0 - 7.4.2 and more versions
    Versions available for JIRA Server 6.3 - 6.4.14
    JIRA Service Desk
    This app is compatible with JIRA Service Desk.
    Allenta Consulting S.L. (CIF ESB15974553) supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.
    JIRA Service Desk
    This app is compatible with JIRA Service Desk.

    JIRA add-on allowing the reception of GitLab push events using GitLab project web hooks

    JIRA add-on allowing the reception of GitLab push events using GitLab project web hooks

    Integrate GitLab CE / EE changesets in JIRA

    ​Almost no configuration is required!

    Don't miss a single commit

    Include JIRA issues in your commit messages, push changesets to GitLab CE / EE, and automatically generate JIRA comments, work logs, workflow transitions... referencing those changesets and linked to JIRA users.

    more »

    For each GitLab project you want to integrate in JIRA, simply set up a web hook in order to submit all push events to the listener add-on running in JIRA.

    more »

    Define several fallback JIRA users to be used when e-mail addresses in pushed changesets do not match any JIRA user.

    Secure the connection between GitLab and JIRA using HTTPS and a shared secret.

    more »

    More details

    GitLab Listener is a JIRA add-on allowing the reception of GitLab push events using GitLab project web hooks. This add-on allows integration of commits pushed to GitLab inside JIRA issues.

    Issue keys are extracted from commit messages; then, these messages are logged as JIRA comments, activities, work logs and / or workflow transitions linking back to the GitLab changesets.

    GitLab includes a basic GitLab-JIRA integration. This add-on extends that basic integration allowing you to:

    • Reference multiple issues in a single commit message.
    • Use commit messages to execute any workflow transition (i.e. not just closing issues).
    • Use commit messages to generate worklogs (i.e. time tracking).
    • Restrict visibility of comments, etc. generated by the add-on to a project role.
    • Select between generating JIRA comments or JIRA activities.
    • Link GitLab and JIRA users instead of generating JIRA comments using a generic JIRA API user as the basic integration does.
    • Support multiple JIRA issue key formats.

    User reviews

    Sign in to write a review
    by Emmanuel Mathot on 2017-08-02
    Great add-on! Would it be possible to have the support with the smart commits comment compatibility? We have different code repo (github, gitlab) and we would like to have a common guideline for comments. https://confluence.atlassian.com/display/FISHEYE/Using+Smart+Commits
    Was this review helpful?YesNo
    Allenta Consulting S.L. (CIF ESB15974553)

    Thanks for the review Emmanuel.

    Adding support for smart commits as described in that URL is not trivial. It could be considered in the future, but it's not a trivial change. Thanks for the suggestion!

    by Adolfo Casari on 2017-08-01
    Is it possible to have all gitlab activity to be posted in an issue tab instead of comments? This way one can see all relevant git activity in a single place.
    Was this review helpful?YesNo
    Allenta Consulting S.L. (CIF ESB15974553)

    Thanks a lot for the review Adolfo! About your question, I'm afraid having all the GitLab activity in a separate tab is not possible. Sorry!


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your host product. For JIRA Server 7.0 or later, the app tier should match the maximum tier of the licensed JIRA products on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of JIRA Server prior to 7.0, the app tier should match the licensed user tier for JIRA. Even if fewer users want to use the app than your JIRA license, the two licenses should match exactly.Note: While this app has features specific to JIRA Service Desk, the app is technically available across the whole JIRA instance. Therefore the above guidelines for the license tier still apply.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

    How can I buy apps for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    Allenta Consulting S.L. (CIF ESB15974553) provides support for this app.

    Vendor support resources


    Find out how this app works.


    Community discussions connect you to the vendor and other customers who use this app.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.


    Version 2.0.10 JIRA Server 7.0.0 - 7.4.2 Released 2017-04-20


    Upgrade to AO 1.2.0 (JIRA >= 7.0)


    Upgrade to Active Objects 1.2.0, including creating of a e composite index in order to boost performance on busy environments.

    This release hopefully will fix the infamous 'PSQLException to be thrown: ERROR: constraint "u_ao_9b0d9b_processXXXXXXX" of relation "AO_9B0D9B_PROCESSED_COMMIT" does not exist"' error.


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate GitLab Listener via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for GitLab Listener. You're prompted to log into MyAtlassian. GitLab Listener begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older GitLab Listener versions compatible with your instance, you can look through our version history page.

    Similar apps