We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps.
Our estimation process is basically as follows:
* Product Manager creates Feature in Aha
* Product Manager send ...
Ability to specify and bulk edit 'run as user' in integrations
We have a small team of people who can create integrations. The integration always sets the user who created the integration as the 'run as' user. When we have staff turnover, we have to manually change the integration 'run as' user. There could b...
about 1 month ago
In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...
over 3 years ago
Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes i...
over 4 years ago
When initially importing Salesforce organizations into Aha!, there are filters to narrow down the records that should be imported. It would be helpful to have filters also available to control automatic imports on a go-forward basis. Using the "Ap...
7 months ago
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
6 months ago
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
DevOps Integration -- Support rendering of images embedded in description field
Currently when you import from Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in DevOps....
As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...