Add missing Rally built in fields "Project" and "Leaf Story Plan Estimate Total" in Aha! under Integration field mapping
The following fields are available in Rally but are not available in Aha to do field mapping under Aha to Rally Integration. Please add these fields so that teams can map them. Rally Built in field names: Project Leaf Story Plan Estimate Total
Uma Prabhala
almost 5 years ago
in Rally
4
Shipped
Re-enable conversion of Features to Requirements when JIRA integration is active
In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
Update Salesforce.com (SFDC) opportunity value automatically from SFDC to Aha! Idea
If we create a feature request based on a SFDC Opportunity, the information presented in Aha (such as dollar value) does not seem to update if that opportunity changes in SFDC. Makes it difficult to determine the actual value of opportunities from...
Suzanne Vaughan
over 9 years ago
in Salesforce
8
Shipped
Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.
Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
Right now you can only define default values for TFS fields. It would be better if there was a way to map fields in AHA to fields in TFS, including custom fields. This could be done by using variables (aka: {{Assignee}}) in the current UI or provi...
Add support for linking to multiple different JIRA issue types
We would like to roadmap product releases with new up-coming features and bug fixes. Aha features currently map to Jira stories but we'd like to map to Jira 'Bug' and possibly 'Improvement' types as well.
Map feature "Value" field in Salesforce integration to a custom field instead of the opportunity value
We need a tool that helps us quantify the potential value/ROI of a feature (to the extent that this is possible...). The SF/Aha! Integration ties to the standard opportunity amount field in SF, but that field is not the metric that we care about i...
Support Azure DevOps integrations for parent and child records across workspaces
What is the challenge? When a parent or a child record is moved to another workspace in Aha! it will no longer update via integrations due to the child and parent existing in different workspaces in Aha! What is the impact? Integrations break when...
For Project Status, currently the only information we have is feature and requirement status coming from Aha to VSO / VSTS and vice versa. It would be far better for businesses tracking effort to be able to put estimates into either tool synchroni...