Allow attachments to Feature comments to be integrated to Azure DevOps
When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
John Biltcliffe
over 5 years ago
in Jira
4
Future consideration
A lot of project management tools have bad road maps. Investigate those with bad road maps and attempt to integrate with the platform.
There should be two options. Use the entire project as a road map or select one task and use the subtasks as ...
Every time an issue is updated in Aha, the user must remember to click on Actions and send the update to Gitlab. This manual step is different than making all other edits in Aha that automatically save and makes it easy for things to become unsync...
Guest
over 7 years ago
in Integrations
5
Future consideration
We are trying to close the feedback loop for our customers. As product ideas come in through ZenDesk, they are kicked to Aha! and then the product team updates each ticket with a status. That status, while reflected in the ZenDesk issue detail, do...
Guest
almost 10 years ago
in Integrations
2
Future consideration
Map VSTS/TFS picklist custom fields to Aha! choice list fields
VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), each i...
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...