Custom Record Type, Made Up Entirely Of Custom Fields
We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...
Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...
Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
Add ability to customize the "Integration updates" modal
Request the ability to customize what is displayed and in what order on the "Integration updates" modal. We are integrated with Azure DevOps (ADO) Services, so our specific request is to display the ADO ID at the top level on this modal. It will m...
In ADO we use assign our epics as children of themes. In AHA we map themes to initiatives and epics to releases but in the integration configuration we cannot set the parent mapping.
Azure DevOps or JIRA integration : allow some way to automatically select which integration to use when more than one exists in a product
We usually map 1 Aha Product to 1 AzDo project, in which case everything is fine (except that everything ends up in the same Area Path). We can also easily map N Aha Products to 1 AzDo project, mapping each Product to an AzDo area path. But we cur...
Annoying maintenance task of updating expired webhooks that keep making systems out of sync and we end up using VSTS as the source of truth rather than Aha!
I'm not sure how much demand there would be for this, but I've had a need a few times for it so I'm going to suggest it. I would like to be able to limit automatic integration of new requirements if they are in a certain state, such as New. If a f...