Simple to enjoy. No, I am not referring to my morning cup of coffee. I’m reminiscing about a few of my favorite features I worked on as a product manager. What made them so enjoyable? It was not the technology. The common theme was awesome collaboration between product and engineering.
When everyone is on the same page, the end result is a beautiful thing for customers. That is why at Aha! we continue to invest in features that improve collaboration between product managers and engineers.
Today, we are excited to announce a new two-way integration with GitLab. GitLab provides tools for Git repository management — from code reviews to issue tracking and more. And more than 100,000 companies use GitLab to create and manage code bases collaboratively.
Now you can do your planning in Aha! then easily send features and requirements to GitLab. As engineers complete work, the status is updated in Aha! — ensuring the teams are always in sync.
Here is how you can get started using Aha! and GitLab together:
Do your planning in Aha!
You need to complete your planning before you can send a well-vetted release over to the engineering team in GitLab. Do your planning first in Aha! — create your product roadmap, define individual features, prioritize the backlog, and move features into a release as you prepare for development.
Plan your releases in Aha! using the feature board and prioritize work based on scorecards.
Send features from Aha! to GitLab
Once you complete your product roadmap and feature planning it is time move features from Aha! into GitLab for the engineering team to work on. You can send features individually or in bulk as a sprint or release.
The following information is sent from Aha! to GitLab via the Actions menu: Feature or Requirement name, Description, Attachments, and Status.
Send status updates from GitLab to Aha!
As the engineering team completes work, status updates can be sent back to the product team in Aha! using status labels. When “Add status labels” is enabled, the status of the feature will be added as a label in GitLab. To change the Aha! status, simply change the label in GitLab. For example, to change the Aha! status from Ready to develop to In development, remove the GitLab label Aha!:Ready to develop and add the label Aha!:In development.Status updates are sent back to Aha! by updating the label in GitLab. Only one label with the prefix “Aha!:” will be allowed on a GitLab issue.
You must be a Product Owner in Aha! to configure the GitLab integration. Once configured, you can save the configuration as a template by selecting Use as template from the Actions menu. Saved templates will be available to use for future GitLab integrations.
To configure your GitLab integration, navigate in Aha! to Settings > Product > Integrations.
With so many integrations, it is easy for product managers to set brilliant product strategy and to share visual roadmaps in Aha! while engineering teams work in the tool of their choice.
That is why we are happy to introduce the new GitLab integration. And why we remain dedicated to expanding the ecosystem of development-oriented tools that can integrate with Aha!
Sign up for a free Aha! trial — be happy
This GitLab integration is available to all Aha! customers. If you are not already an Aha! customer, you may want to sign up for a free 30-day trial of Aha! now to see why over 50,000 users trust Aha! to set product strategy, create visual roadmaps, and prioritize releases and features.