Order portfolio items in Rally according to their rank in Aha!
When creating or updating a record in Rally set the rank of that record according to the corresponding rank in Aha!. This can be done using the rankAbove/rankBelow parameter using a similar technique that is used by the JIRA integration. Changes t...
Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use ...
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...
Mapping of Initiatives to other ticket types in Jira
Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...
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...
Rally integration: support updating of release dates
While the current Aha! -> Rally integration does support Aha! creating a release with a release date in Rally when the initial send is made, any updates to the release date in Aha! are not updated in Rally. To be consistent with other integrati...
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 ...
ideas linked from zendesk ticket reports should not expose part of the email address to other public users
When a zendesk ticket is linked to from zendesk, the aha zendesk plugin only records the email address associated with the linked zendesk ticket reporter to make the link and does not send the name field value to the Ideas portal user entry.
As su...
allow clicking on JIRA ticket-id in feature_grids view
right now if i add the column "jira key" (or even jira-link), and i want to see the ticket in jira, i have to copy it from the UI, and go to JIRA to paste it (or my browser's URL) to see the ticket in JIRA.this can be solved by making the col to b...