Skip to Main Content
Status Future consideration
Categories Integrations
Created by Fabio Brito
Created on Oct 20, 2019

Integration 2.0 for Gitlab

Gitlab is an important integration, but still not covered by the new 2.0 integrations

  • Attach files
  • Peter K
    Dec 28, 2021

    Absence of this feature is preventing expansion of our Aha account. We really want to be able to use the reporting and feature organization capabilities of Aha, but the current integration does not have the functionality that makes this possible. Specifically, we need:

    • Ability to link Aha features to existing gitlab issues

    • Mapping of gitlab epics to Aha epics

    • Notifications of changes made in both platforms before synchronizing between them (sync requires approval)

    • Better tag mappings - optimally, this would include workflow tags for Aha

    • Issue import. Being able to import issues from our existing projects would allow us to report on them properly

    Gitlab is continuing to expand support for project and product management (https://about.gitlab.com/direction/dev/#plan), and it has really great capabilities for automated release management. Aha + gitlab could be a gold standard for enterprise software development if gitlab had the capabilities of other 2.0 integrations.

  • Nir Soffer
    Jun 22, 2021

    seconded - gitlab support without epics is a bit a challenge; in addition comment syncing; ability to sync labels to statuses; and having a swimlane feature in aha that is based on label rather than aha status.

  • Peter Rietzler
    Feb 4, 2021

    We are using AHA for quite a few years now and are eagerly waiting for upgrades on your GitLab integration as it has quite some problems that trouble us:

    Comments are not synced (in neither direction)


    It overrides the description - especially the state of the requirements checkboxes - each time when we sync from AHA to GitLab. This is quite nasty as also the state of the requirements checkboxes in the GitLab issue description is not synced back to AHA and we lose the state managed in the GitLab issue every time.


    The format of the description in the GitLab issue has problems. Starting with the fact that there is no newline between the requirement title and the requirement description and continuing with various formatting problems. It often just looks ugly in GitLab


    Order of features and GitLab issues is not synced in any direction which causes a lot of duplicate work in backlog priorisation

  • Christophe Deliens
    Oct 21, 2020

    My wishlist of missing features for this integration would be:

    • import existing Gitlab issues to Aha;

    • allow changing Gitlab label to update the Aha feature status;

    • support "Group" milestone.

    Happy to discuss this further! Thanks 👍🏻

  • Fabio Brito
    Jun 4, 2020

    Any update on this? Been quite a while now.

    Gitlab is still one of the major systems that don't have integration 2.0.

  • Guest
    May 7, 2020

    ..sorry the "Silver" account on Gitlab

  • Guest
    May 7, 2020

    Our development organization just upgraded to the "Silver" account on Github, which allows the definition of Epics in Gitlab. It would be great if we could integrate with Aha by mapping Features with Gitlab Epics, and Requirements with Gitliab Issues. Right now, the Aha integration does not allow for this.

  • Guest
    Mar 27, 2020

    As a result, if a child issue is created in GitLab, for two parents that are already linked in Aha!, that new child issue will NOT automatically appear in Aha. It doesn't even show up in "Integration updates"....

1 MERGED

Enable Gitlab Epic Integration

Merged
I want to be able to send the Epics created in AHA to Gitlab
Guest 6 months ago in Integrations 0 Future consideration
9 MERGED

Allow Aha to connect with exiting issues in Gitlab

Merged
This is available for Asana and Jira, but not for Gitlab
Fabio Brito almost 3 years ago in Integrations 0 Future consideration