Who would benefit? Anyone who wants to send an audit record of full item state on change What impact would it make? Default should remain only changed columns to avoid making this a breaking change. Full state will obviously generate a larger payl...
Sandy Teenan
11 months ago
in Integrations
0
Future consideration
I currently have over 4000 items in the integration updates section. If I am looking for something in particular based on a key word (or want to import a few based on a key word) it would be GREAT to do a search in window.
Guest
about 6 years ago
in Integrations
4
Future consideration
Idea integration with Vivun Hero's Opportunity Gap functionality
Vivun Hero is a presales-focused bolt-on to Salesforce which allows SCs/SEs to tie product gaps to opportunities -- to provide reporting to Product on revenue at stake with those gaps. Having a more direct integration to be able to tie Aha! ideas ...
Guest
almost 2 years ago
in Integrations
0
Future consideration
Allow the mapping of Products in Aha! to Component/s in Jira.
In order to automatically assign Aha! items pushed over to Jira to the right component, I've had to create a custom field in aha! with a pick-list of the component names from Jira. I c...
Max Cascone
about 7 years ago
in Jira
3
Already exists
Allow users to refresh all Aha! features from a linked JIRA integration.
Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow
about 9 years ago
in Jira
0
Already exists
Allow two-way integration for picklist fields in Azure DevOps when using the XML process model
This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...
I am unsure why this feature was designed this way; However, when creating and pushing a release from Aha! to ADO, it should honor the area path set up in the Aha! to ADO integration. Furthermore, when linking to an existing iteration in ADO, the ...
Our company has recently transitioned from Salesforce to SAP C4C. In this, we have lost integration between our CRM tool and Aha. It would be great if there was a C4C <> Aha integration for cases as there is for Salesforce.
Daniel Scudds
over 5 years ago
in Integrations
2
Future consideration
Nested Iteration Paths with VSO / Visual studio team services integration
We have the same VSO project for many products in Aha. We would like the ability to have child iterations for releases so we can group them together in our queries. Current integration only allows us to go 1 level deep in the iteration path.
Our...