Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 271

Add Intiative -> Solution Capability mapping to Feature -> Feature options

There was a prior Idea that requested and closed as Delivered, however it wasnt delviered as asked for. The goal was to allow us to map Intiatives into Rally as Solution Capabilities, Features to Features (under those Solution capabilties in Rally...
Guest almost 8 years ago in Rally 0 Shipped

Need additional integration with Rally - Moscow Field

We current use the Moscow filed within Rally (Must, Should, Cloud, Won't) to give our teams directions on priorities set by product management. We would like to have these field populate within Aha, and able to have the 2 way integration. This wou...
Guest almost 8 years ago in Rally 3 Shipped

Need Aha! Requirement --> Github Issue and EXCLUDE Aha! Feature --> GitHub Issue

If you look at an Aha! Feature as a container of requirements, e.g. Aha! Feature with 3 requirements, then when you send a in the : Feature—>Issues, Requirements —> Issues; then you end up with 4 issues in GitHub - when you only need 3. ...
Jonathan Ross almost 8 years ago in GitHub 2 Shipped

Append Aha! feature ID to Rally feature description or other field

No description provided
Guest almost 8 years ago in Rally 0 Shipped

Create/update tags in Aha!/Rally and have that flow to Rally/Aha!

Synchronize the Aha! feature "Tags" field with the "Tags" field for portfolio items in rally. The sync should be two-way. Tags are not synced for any Aha! record types other than features.
Guest almost 8 years ago in Rally 0 Shipped

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...
Guest almost 8 years ago in Rally 1 Shipped

Sync releases with epics in the JIRA integration

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 ...
Guest almost 8 years ago in Jira 3 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...
Mike Ward almost 8 years ago in Jira 4 Shipped

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...
Ray Yee about 8 years ago in Jira 1 Shipped

Synchronize Effort and Remaining Effort to VSO

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...
Guest about 8 years ago in Azure DevOps Services and Server 0 Shipped