Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
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
over 3 years ago
in Rally
2
Future consideration
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
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...
Allow custom integrations to behave like built-in Integration 2.0
Who would benefit? Companies that use dev tools that aren't supported by Aha! What impact would it make? Removes lots of manual work and improves UX for custom integrations. How should it work? Allow adding custom integration with a name and icon....
Alexey Zimarev
4 months ago
in Integrations
0
Future consideration
The names of the people we do business with is very important. The Salesforce integration should sync the contact names of our clients in Salesforce with the Ideas portal to enure consistancy and data consistancy.
Daniel Lynch
over 2 years ago
in Salesforce
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 M...
When, for example, an idea is created within aha! and the integration alerts a slack channel of this entry, it would be good to be able to customise the output of that notification and remove unwanted fields.
Guest
about 3 years ago
in Slack
2
Likely to implement
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S
over 2 years ago
in Jira
0
Future consideration