Add the ability to combine fields with GitHub Integration
We need the ability to send more information from Aha to GitHub, this would include the Due Date. We need the ability to combine fields from Aha to a single GitHub Field. E.g. Send Title + Due Date in Aha to the Title Field in...
George Champlin-Scharff
about 7 years ago
in GitHub
0
Future consideration
Our product team has just started using aha to keep track of product development. Mean time in the individual teams we are free to choose what ever tool we like and fits our needs, and for that I've chosen coda.io. Coda.io have a feature where you...
Guest
about 7 years ago
in Wanted
1
Already exists
Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
We use the Github integration for a few of our projects. I have it configured to import Features to Issues and Requirements to Issues.
It would be very helpful to exclude some records during the import process. For example, I recently sent a Featu...
Guest
over 7 years ago
in GitHub
2
Future consideration
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Provide applicable error message when a Jira integration can't authenticate due to a captcha challenge issue
When attempting to set up a Jira integration, authentication can fail with a 403: CAPTCHA_CHALLENGE error we can see in the logs, but there is no applicable message on the integration-set up screen. It just says "We could not connect to your Jira ...
Emily Yankush
over 2 years ago
in Jira
0
Future consideration
Integrated icon or color on release column of board views to show integration linked
My users are expected to help keep their roadmap releases integrated to the tools of the engineering team (jira or Azure Devops). They need to link the release to the jira release or ADO iteration path, to keep roadmaps and scope alligned in both ...
Kevin Martin
over 2 years ago
in Integrations
0
Future consideration
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
almost 5 years ago
in Jira
0
Future consideration