Ability to remove stories that are in the integration from Aha!
Often times we only want a subset of what's in Aha! in our JIRA project. In some cases, when things get deprioritized, we want to remove them from JIRA but keep them in Aha! Would love the ability to do that FROM Aha! because keeping things in syn...
Guest
about 4 years ago
in Jira
0
Future consideration
In GitHub integration, we would like to map a custom field called "Repository" to a static value that is identical for all issues from the one GitHub integration. That way we could then show the value as a label and also filter by it in feature vi...
Guest
about 4 years ago
in GitHub
0
Future consideration
Select workspaces that ideas can be created/searched through Zendesk integration
We'd like a similar feature to the Salesforce integration where we can choose which workspaces ideas are added and searchable in the Zendesk integration. For a variety of reasons, we have ideas in several workspaces, but we only want ideas to crea...
Steven Chan
over 4 years ago
in Integrations
0
Future consideration
It would be great if the "to-do's" in AHA Requirements, can be mapped to Rally as "to-do's" in the users stories. And, update both ways if marked as completed. Here is a similar idea for Azure DevOps; it would be great to see this for Rally as wel...
Guest
over 4 years ago
in Rally
0
Future consideration
Allow 2-way integration to Jira FixVersion/s field from text field
Instead of having to integrate Aha! Release to Jira FixVersion/s, let Aha! text fields specify the name of a version and have it update the FixVersion in Jira based on a matched name. If no matched name exists, then throw an integration error just...
Jor Bratko
over 4 years ago
in Jira
0
Future consideration
Pivotal Stories added to Epics converted to Requirements in Features
The Pivotal integration is good, but fails to capture a common case for us. Our teams often add new Stories to Epics that are essentially Requirements on the corresponding Feature. We track progress through these Stories/Requirements. Right now, t...
Christopher M
over 4 years ago
in Pivotal Tracker
0
Future consideration
We use Bugsnag to detect and diagnose bugs & issues. It would be great to link these directly with Aha, similar to how it integrates with JIRA, GitHub, Trellor, PivotalTracker.
Bugs and issues are a key part of the roadmap.
Guest
over 8 years ago
in Integrations
0
Unlikely to implement
Microsoft Teams - (365), allow presentation of notebooks or roadmap slides
Microsoft Teams is now available and currently supports hooks for Aha for data feeds.
Microsoft Teams also supports the ability to populate a Tab. Currently they have support for the VSO Kanban board, Power BI, Excel, etc. It would be great if you...
Guest
over 8 years ago
in Integrations
0
Already exists
Would it be possible to not need a paid AHA account to process VSTS updates?
At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...