I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
Guest
over 9 years ago
in Integrations
11
Already exists
Ability to filter records in the ‘integration updates’ based on a field (eg: categories or tags)
Currently Integration update brings in all new records from Rally project. And there is no way to filter the data before import. Want the ability to filter on some Rally fields (eg. status & tags) which will help to import on the required reco...
Jyothirmayi Talaparthy
about 4 years ago
in Rally
2
Future consideration
Show name of user whose token is being used in ADO integration
Who would benefit? Admins of accounts with ADO integrations What impact would it make? When an ADO integration is created, a user with the correct permissions must enter their token to authenticate the integration. However, the token owner's name ...
Who would benefit? all teams and aha What impact would it make? It would allow admins to stop a job from running such as an import when it is realized an integration was set up wrong etc. This will benefit aha because it will prevent unnecessary p...
Guest
9 months ago
in Integrations
1
Future consideration
Mural is a great visual management tool. Ideally Mural could be the foundation for the notes section in Aha!. Ideally....you could work on a Mural from within Aha!...so perhaps an integration of some sort. This allows for a virtual room where team...
Guest
almost 7 years ago
in Integrations
2
Unlikely to implement
Add better error handling for 'unhandled error exceptions'
When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
Guest
about 1 year ago
in Jira
0
Future consideration
Allow additional Link Types in the 'Links to' field
Within AHA we are mapping
Releases -> ADO Release Work Item
Master Feature -> ADO Epics
Features -> ADO Features.
Master Features need to be located in the Release in which they complete. But Features (that contribute to this Master F...
Support configuring capacity units of time for ADO server integrations
What is the challenge? Currently the "Configure" option to select units of time to send estimates to ADO is only avaiable on the ADO Services integration and is not available for users using the Server integrations. What is the impact? Users are u...
Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...