You have already this for Github but not for Gitlab For organization deployed Gitlab in their own environment, it will be quite useful.

Who would benefit? Companies that use dev tools that aren't supported by Aha! What impact would it make? Removes lots of manual work and improves UX for custom integrations. How should it work? Allow adding custom integration with a name and icon....

Use is all of the time. Be fantastic to be able to create a Notebook in it hooked up to Aha! much like you do a Jira product but 2 way.

Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...

After the updated TFS integration which allows records to be imported directly from TFS into Aha. It would be ideal to be able to search the new record list for key words. Currently you can filter the list but this is not very user friendly and if...

Who would benefit? Anyone with a GitHub Integration What impact would it make? Right now, the syncing of an Aha! Item Requirement's tag is not supported. This means any requirement that the visibility of tags on a requirement is lost in GitHub if ...

Our company uses SugarCRM to manage the business side workflow and tasks. We are looking for a product management tool that will integrate with SugarCRM. It should allow our business team to pass in ideas through Sugar and then Aha to pass updates...

Items are prioritized in Aha's release area by the Product Manager. When sending the release to Pivotal Tracker, the Stories that appear in PT are in reverse order, meaning the engineering team must spend time comparing lists to fix the order. I e...

We often create features in Aha and sync them into DevOps for the Dev Team. Our dev team then creates the user stories and syncs those back to Aha. They use a small grid in their user story template in DevOps. When it syncs back, that grid is oddl...

Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it. With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...