Skip to Main Content
Status Future consideration
Categories Ideas
Created by Guest
Created on Jul 27, 2017

Improve Gitlab Integration

Every time an issue is updated in Aha, the user must remember to click on Actions and send the update to Gitlab. This manual step is different than making all other edits in Aha that automatically save and makes it easy for things to become unsynchronized. I suggest that once and issue has been submitted to Gitlab, any subsequent edits should propagate automatically.

Features created in Aha and sent to Gitlab issues can be modified and saved in Gitlab, but the changes do not show up in Aha. There is some kind of reminder pop up that alerts the user of a discrepancy, but the only option seems to be to manually diff the two records and manually fix it in Aha. Ideally things could change in either tool and update the other, but a compromise might be to create the Gitlab issues so that only the labels can be modified to propagate status back to Aha.

  • Attach files
  • Fabio Brito
    Jun 4, 2020

    Also connected to Integration 2.0 for Gitlab

  • Guest
    Sep 20, 2019

    +1 to sync without Aha!: labels.

  • Guest
    Sep 20, 2019

    Would love to have GitLab Issues mapped back to the features in Aha!, meaning whenever an issue is created in Gitlab under a milestone that was created by Aha, these issues should show up as features in Aha.

  • Guest
    May 3, 2019

    And add the description and comments to the integration.

    Maybe the requirements can be checkboxes in the description of gitlab.

  • Daniil Novikov
    Nov 29, 2018

    Would be great to synchronize status updates between gitlab and Aha! without Aha-specific labels e.g. 'Aha!:'

  • +2