When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...
Rally integration: Add support for custom field integration mappings for two-way custom field updates
We recently made the update where we can populate a required custom field in Rally with a default value to facilitate the integration with required custom fields. This idea is to take it a step further and provide custom field integration mapping ...
Allow initiatives to sync to integrations as a first class object like features, requirements and releases. For the JIRA integration this would involve: 1. Allow the user to choose the JIRA issue type to sync initiatives with in the integration co...
Add an "Import from Rally" utility for uploading the Rally backlog into Aha!
Add an "Import from Rally" utility for importing existing features, user stories, etc. and supporting metadata into Aha! as Features and Requirements and creating corresponding links between the data objects in support of the bi-directional integr...
Currently the Aha! to Salesforce integration must be installed using the classic interface. After that, it can be used via the Lightning interface. As a Salesforce admin, it would be nice to be able to install the app via the Lightning interface a...
Scott Goldblatt
almost 8 years ago
in Salesforce
15
Shipped
We would like the ability to have new records created in JIRA/Rally automatically import into Aha!
Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
Danny Archer
almost 7 years ago
in Integrations
7
Shipped
Link existing GitHub issues with a new Aha! Feature
The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status
When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow.
It would be great to also access the Resolution status from Jira to handle this case.