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, ...
over 4 years ago
As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release
Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match
If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
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 conf...
Ability to map standard fields in Aha to custom fields in JIRA
It would be really useful if I could map standard fields in Aha to custom fields in JIRA. For example...- Assigned User to Product Owner- Aha Score to Business ValueThese are fields that we use in JIRA that we are having to manually type in again....
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 c...
about 5 years ago
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The ...
over 4 years ago
Add support for linking to multiple different JIRA issue types
We would like to roadmap product releases with new up-coming features and bug fixes. Aha features currently map to Jira stories but we'd like to map to Jira 'Bug' and possibly 'Improvement' types as well.
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...