Gitlab is an important integration, but still not covered by the new 2.0 integrations
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.
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.
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
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.
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"....
I want to be able to send the Epics created in AHA to Gitlab
Guest
about 3 years ago
in Integrations
0
Future consideration
10
MERGED
Allow GitLab issue label synchronisation to Aha status
Merged
On Aha, when adding a GitLab integration, I can only map the GitLab issue state (open, closed) with Aha.
I would like to be able to map specific GitLab labels to specific Aha statuses.
E.g.:
map GitLab's "Workflow::Doing" to Aha's "In development...
Christophe Deliens
over 5 years 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
over 5 years ago
in Integrations
0
Future consideration
30
MERGED
Improve Gitlab Integration
Merged
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 unsync...
Guest
almost 8 years ago
in Integrations
5
Future consideration
2
MERGED
Fix GitLab Integration
Merged
Let’s say a developer wants to change the label from “in development” to “ready to ship”, he has to un-mark the “in development” label and only then mark the “ready to ship” label, instead of just changing it. If I’m rephrasing it – using only a s...
Guest
about 5 years ago
in Integrations
0
Future consideration
18
MERGED
Gitlab - Connect Master Features to Epics, and more
Merged
As one more request to improve connection between Aha and Gitlab :) We need better integration between Master Feature, Features and Requirements of Aha to Epics and Issues of Gitlab. A sample could be Master Features -> Epics and Features/Requi...
Fabio Brito
almost 5 years ago
in Integrations
3
Future consideration
18
MERGED
Gitlab import of issues as features in aha
Merged
It should be possible to import issues from gitlab into aha as feature.
Guest
over 6 years ago
in Features
4
Future consideration
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.
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.
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
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 👍🏻
Any update on this? Been quite a while now.
Gitlab is still one of the major systems that don't have integration 2.0.
..sorry the "Silver" account on Gitlab
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.
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"....