505
Customers have installed this add-on in at least 505 active instances.
    by Allenta Consulting S.L. (CIF ESB15974553)for JIRA Server 7.0.0 - 7.2.6 and more versions
    Versions available for JIRA Server 6.3 - 6.4.14
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Allenta Consulting S.L. (CIF ESB15974553) supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    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

    (8)
    Sign in to write a review »

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

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

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

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

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

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

    Learn more

    Support

    Allenta Consulting S.L. (CIF ESB15974553) supports GitLab Listener. You can visit the support site to get help.

    Get support

    Versions

    Version 2.0.9 JIRA Server 7.0.0 - 7.2.6 Released 2016-06-23

    Summary

    Support decimal values in #time directive (JIRA >= 7.0)

    Details

    Support decimal values in #time directive as described in https://github.com/allenta/gitlab-listener/issues/38.

    Installation

    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 add-on 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 add-ons