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
over 8 years ago
in Jira
17
Shipped
Sync record's workspace, goal, initiative, epic, and release (name and link) to integrations
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker
over 6 years ago
in Jira
14
Shipped
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...
Our organization is moving from Slack and into using Microsoft Teams. We would like to have our Aha! activity feed integration be compatible with Teams.
Jon Kremer
about 8 years ago
in Integrations
20
Shipped
Ability to link features/requirements to existing VSO work items
Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful