Skip to Main Content


Showing 933

Showcase Github Comments in Separate Thread

Our QA team has a hard time seeing the story of a ticket due to all of commit messages. It would be nice if instead of appearing as just comments the Github commits appeared separately or were able to be be filtered out.
Guest over 5 years ago in GitHub 0 Future consideration

Converting requirements to features after integration

Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external syste...
Tom Beck over 5 years ago in Azure DevOps Services and Server 1 Future consideration

Prompt before committing bulk changes from Integration Updates screen

The Send Changes command on the Integration Updates screen should really prompt a user to confirm when making bulk changes. I inadvertently selected it instead of the Ignore command for 30+ features and promptly update my JIRA instances -- which i...
David Vins over 5 years ago in Integrations 0 Future consideration

Map custom fields to tags/labels in external integrations

Current implementation only allows tags to be mapped to Labels (e.g. in Trello) As a result custom fields (e.g. predefined list of components) cannot be exported to external integrations, unless they explicitly support custom fields on their own....
Guest over 5 years ago in Integrations 0 Future consideration

VSTS Integration - Error importing new records into Aha

As we are starting to use more and more Aha!, we are seeing errors while newly created records by Development team in VSTS being imported into Aha!. 2 main reasons for the errors include Feature is not available for the user stories (Requiremen...
Sekhar Nallapaneni over 5 years ago in Azure DevOps Services and Server 1 Already exists

GitHub Commit Hook shouldn't add commenting user as a watcher (or shouldn't run as user)

When the GitHub Commit Hook is run, it adds me (the user who created the integration) as a watcher on whatever features are referenced. This becomes a huge notification nightmare pretty quickly. It would be great if the comments on features as a...
Guest over 5 years ago in GitHub 0 Future consideration

JIRA integration: support mapping of “Release name” into custom field

Mapping of “Release name” towards custom fields in JIRA integration instead of “fixed version” or “affected version” only currently the AHA-Jira integration only allows a mapping of "release name" values in either "fix version" or "affects versi...
Florian Kette almost 6 years ago in Jira 1 Unlikely to implement

JIRA Tree CustomField

Support in the v2 JIRA API for JIRA field types of Tree CustomField (multiple choices).
Guest almost 6 years ago in Jira 0 Future consideration

Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query

Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc. Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha. Requirement: The query should bring...
Guest almost 6 years ago in Jira 0 Unlikely to implement

Add batch API endpoints for Add, Update, and Delete interactions

As a heavy user of the REST APIs to aggregate and disseminate information across multiple systems, I would like to have a batch API endpoint for updating Features in order to avoid Throttling limitations in the existing one-update-at-a-time REST i...
Guest almost 6 years ago in Integrations 2 Unlikely to implement