RELATED IDEAS
Gitlab - Connect Master Features to Epics, and more
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/Requirements -> Issues. (although Requirements mapping for sure need better integration, since labels and status don't synch)
Hope integration 2.0 is on its way, all related:
https://big.ideas.aha.io/ideas/A-I-8373
https://big.ideas.aha.io/ideas/APP-I-4879
https://big.ideas.aha.io/ideas/APP-I-7030
© 2024 Aha! Labs Inc.•All rights reserved
I have used the other dev tool to aha! integrations and been pretty impressed. this leaves a lot to be desired. I really need the features in aha to be able to link to epics in gitlab and then the stories to follow.
We have the same challenge and have now unfortunately stopped using Features in Aha!. We go from Ideas to manually creating Epics in GitLab. Gitlab is becoming our main place to manage Epics. Its too bad, as we like Aha! for many other reasons. We use Ideas and create Releases to track and communicate them at that level. The Releases are just a short text description and release dates with no Features (as those are now Epics in GitLab).
We have also a big issue with that, as Aha! can not sync Epic (former Master Features) with Gitlab or even create Epics in Gitlab. Furthermore if development promotes Features to Epic in Gitlab, your former feature will be closed in Gitlab and automatically in Aha. No sync anymore. Then you have Epics with Features (created in Gitlab under the EPIC) in Gitlab without anylink to Aha!. Your Product Backlog run out of sync with what development is doing in Gitlab.