Two Way Jira Sync for Initiative/ Epic custom fields
As far as I am aware you can only map feature custom fields, and I'd like to be able to maintain due dates, team and other custom fields at the Initiative level.
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...
Guest
almost 9 years ago
in Integrations
0
Shipped
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, ...
Cynthia Countouris
almost 9 years ago
in Jira
17
Shipped
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...
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...
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 9 years ago
in GitHub
2
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.
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 ...