Integrate Aha! With GitLab
GitLab is an open source tool used by developers to create and manage code bases collaboratively. Built on Git, which is a very popular and efficient distributed version control system, GitLab gives you all the tools needed for Git repository management from code reviews to issue tracking and more. GitLab also has built-in Continuous Integration and Continuous Deployment to test, build, and deploy your code.
This two-way integration allows you to push your features and requirements in Aha! into GitLab as issues and get status updates back. When you have completed your product roadmap and feature planning in Aha! you can move features into Issues for the engineering team to work on. You can send them individually or in bulk for a release. This makes it easy for product management to set brilliant product strategy and share visual roadmaps while engineering can continue to work in GitLab Issues.
You need to be a product owner in Aha! to set up this integration.
Please carefully follow these instructions to ensure that the integration is properly configured.
Step 1: Create the integration in Aha!
- Enter your GitLab Personal Token. Click the Test connection button
- After a short delay, you will be able to choose the project the issues will be created in.
- Enable the integration.
- Test the integration by going to one of your features in Aha! and using the Send to GitLab Issues item in the Actions menu on the features page. You should then look at your repository in GitLab and see that the feature (and any requirements) were properly copied to issues.
Step 2: To receive updates when an issue is changed on GitLab you have to setup a webhook for the GitLab repository.
- In Aha!, copy the Webhook URL from the GitLab issues integration settings.
- On GitLab, go to the settings dropdown and select Webhooks .
- Paste the Webhook URL into the URL field and leave the secret field blank. Uncheck the "Push events" box, and check the "Issues events" box for the trigger.
- Finally, click Add webhook.
In the GitLab issues integration settings, you can choose to which Aha! status the "Open" or "Closed" state of an issue should map.