Enable tags to be a selection for Azure DevOps integration of requirements
What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
What is the challenge? use the right API calls from Atlassian What is the impact? Integration does not work Describe your idea The Atlassian API for getting resolutions for a project does not exist: 404 is the right response from Atlassian May use...
Support large volumes of repos in GitHub integration
My company has been migrating from GHE to GitHub.com, and the default repo permission is set to "internal". This is causing individual users to have access to over 15k repos. In Aha, this large number of repos is preventing users from being able t...
David I.
about 2 years ago
in GitHub
0
Future consideration
What is the challenge? We use checkboxes for our Acceptance Criteria (AC). Sometimes, it makes sense to add additional detailed ACs under a bigger AC. We use an indent for this, however, after Jira sync, these indents are removed. What is the impa...
Manuel Froehlich
5 months ago
in Jira
0
Future consideration
What is the challenge? In Salesforce if I merge an account into another account any ideas that were linked on the source account are transferred over to the target account. On the Aha! side, the link in the proxy vote to the account still points b...
Justin Waldorf
over 1 year ago
in Salesforce
0
Future consideration
I understand it’s possible to link a Salesforce case, account, or opportunity to an Aha! Idea. It would be much more convenient to go the other way around so that you can link an Aha! Idea to Salesforce through Aha. That would prevent us from havi...
Guest
over 7 years ago
in Integrations
1
Future consideration
Removing the link between an Aha Feature and a Jira Epic should clear all fields included in the sync.
What is the challenge? When a Feature in Aha! is unlinked from its corresponding Epic in Jira, fields that were previously synced—such as the Aha! URL—remain populated in Jira. This creates a false impression that the records are still connected a...
Brittani Carmandi-Weber
6 months ago
in Integrations
0
Future consideration
Integration with Smartsheet - Indentation Mapping (Task Name)
What is the challenge? When establishing the integration Smartsheet with Aha!, the integration is very basic. It only allows us to map the information in Smartsheet to one type of item in Aha! (like Releases, Epics, Features ), and it only pulls i...
Albert Pivonka
6 months ago
in Integrations
0
Future consideration
In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana.
An option to map To-dos to Tasks or Subtask would provide a ...
Austin Merritt
about 7 years ago
in Asana / Integrations
4
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...