Provide additional filter/criteria while setting up the Rally integration
Currently, Rally integration is setup at a Workspace/project level. It would help immensely to be able to add additional criteria, like Tags = XXX or Status = 'YYY'. This will help to filter out records that would show up for import. This will hel...
Jyothirmayi Talaparthy
about 4 years ago
in Rally
0
Future consideration
Create option for rule-based logic to trigger integrations
It would be great to apply rules to firing off integration actions to JIRA/Azure DevOps/etc. I currently find myself in a situation where I would like to add a second integration with Azure DevOps(ADO) that ONLY applies to a specific Initiative. T...
Guest
about 4 years ago
in Integrations
0
Future consideration
We are using a different terminology for our ideas portal, especially for the term "idea". We found the customizing options for the ideas portal very beneficial, but the only place we were not able to change the term is in the salesforce plugin. I...
Guest
over 4 years ago
in Salesforce
0
Future consideration
Provide integration between AHA and HCL Compass / IBM ClearQuest
A integration between AHA and HCL Compass / IBM ClearQuest would allow Features/Epics to be shared with the workflow tools Compass and ClearQuest As Product Manager for ClearQuest and Compass we would welcome this integration for our joint custome...
Guest
about 2 years ago
in Integrations
0
Future consideration
Inherit the hierarchy of the area paths from Azure Dev Ops
When integrating with Azure Dev Ops, the area paths should inherit the same hierarchy when represented in Aha. For example, hierarchy in Dev Ops could be: Company/ Company /Functional Area Company/Functional Area/Team The Aha Azure devops integrat...
Enforce required fields when submitting ideas via Slack > Aha! integration
Currently when submitting to an idea from Slack > Aha! required fields are not enforced. Please could you enhance the integration to include this functionality?
Guest
about 5 years ago
in Slack
0
Future consideration
Sync the change of parent link made in Aha! across 2 Azure DevOps integrations
Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Automated access to a workspace when user selects given workspace
This is the proposed Use Case scenario: If a user receives contributor(Product Manager) access in a named workspace Then automatically grant access read access to integration templates Jira/Rally/Github)
Karla Johnson
over 1 year ago
in Integrations
0
Future consideration
When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog
When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...