RELATED IDEAS
Group Level integration in Aha.
Who would benefit? |
All the teams who are using aha and Gitlab setup for their SAFe ways of working |
What impact would it make? |
Streamlined and logical grouping of features which are created in aha and synced to Gitlab |
How should it work? |
Group level setup must be allowed so that all features don't reside in a single project due to the aha limitation Features are usually created at subgroup level as Epic in Gitlab. It would be great if aha can allow group and subgroup level set up as well. I have attached the integration setup picture which shows it can only be setup at project level |
© 2025 Aha! Labs Inc.•All rights reserved
Having a mapping between Aha workspaces and Gitlab groups is really important for any products that have custom-made analytics software included in their backend. For example, every R package must reside inside its own Gitlab repository, else it can't be built via a CI/CD pipeline in Gitlab using common industry-practices. The same is the case for custom-built Python packages, which also reside inside their own Gitlab repositories. So, if those custom-built analytics packages are part of your product, you'll have to integrate all of their repositories and your Aha product workspace, which can get cumbersome.
Additionally, consider applications that are built on top of workflow engines. Those workflows consist of one or many tools where each tool resides inside a dedicated Gitlab repository. If your client supports many workflows, you may have dozens of Gitlab repositories that belong to the same product. Thus, you would currently have to set up dozens of integrations between your Aha product workspace and all of those Gitlab repos, which is impractical.