Support the "links to" field mapping with next-gen templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates.
Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" f...
Allow Slack Integration for To-Do to assign to a person
Love that I can add TO-Dos to AHA from Slack when interacting with a customer or Product team, but would love to be extended so i can include the person I want to assign the todo to, as well as a description of the today. This would really make th...
Chris Stocker
almost 6 years ago
in Slack
0
Shipped
Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes it...
Kathy Landon
almost 6 years ago
in Jira
16
Shipped
Ability to sync more than one Issue Type to a Record
It's critical for us to track bugs/defects in Aha! related to a specific release but these bugs/defects belong to Features that have other WIP Stories. We need to be able to sync different Issue Types from JIRA to the Requirement record in Aha! Th...
Automatically import into Aha! objects that are created in Trello as work gets broken down
The current integration allows features to be sent from Aha! to Trello so that Engineering and other teams can distribute and action the work.
Often additional features or checklist items may then be created in Trello to capture the more granular ...
Aha's public API is key for us to manage our backlog of ideas and interconnect Aha with other systems. Therefore, having the ability to merge ideas in an automated manner (API) would allow us to drive more efficiencies when managing ideas on our p...
When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements
We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.
Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
In TFS one can create personal access token in order to integrate with 3rd party apps.
Would be great if Aha! would accept that token instead of user name and password.
Slack recently launched 'actions' that allow users to do things with messages, similar to built-in actions like adding reactions or message sharing.
These custom actions provide a simple and visual way for people to interact with an app from Slack...