Integrations
Sort by:
Recent
Status:
Shipped
Showing 253
1
VOTE
Support Integration Templates with GitHub
I recently noticed that the Rally integration capability included a way to save that configuration as a template. We leverage GitHub and would like to save configuration templates as well. There will be a number of products to link to repositories...
0
Shipped
166
VOTE
Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT
We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
17
Shipped
1
VOTE
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...
0
Shipped
8
VOTE
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...
3
Shipped
8
VOTE
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.
...
2
Shipped
2
VOTE
1
VOTE
5
VOTE
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...
1
Shipped
18
VOTE
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 ...
3
Shipped
50
VOTE
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...
4
Shipped