Allow Integration variable on Create Record layout
Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
Filter capabilities on the Integration Update Import screen
As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
Automate service account password updates for TFS integrations
Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
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!
Allowing integration configuration to use queries to limit dataset integrated.
We have a shared devops environment that is managed by others and possibly not configured in the optimal way - especially when we try to integrate. Ideally, the same queries we use to "import" data (that we can modify) could persist to limit the d...