When a change is made in Rally, the Notification message always states that the user whose account is used for the integration to Rally is the one that made the change. This is not useful. Therefore I request that the name of the user in Rally who...

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

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...

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.

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...

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...

As an Aha user and git user I often want to sync certain stories or issues from github but not others. introducing a filter by label would allow me to sync a subset of issues only and avoid the confusion of task and bug issues in my Product tool. ...

Who would benefit? Anyone who wants to send an audit record of full item state on change What impact would it make? Default should remain only changed columns to avoid making this a breaking change. Full state will obviously generate a larger payl...

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...