Integrations
Sort by:
Trending
Status:
Future consideration
Showing 950
4
VOTE
Provide a warning explaining consequences when changing the workflow used in a workspace
When a user moves to a new workflow in a workspace or team, there can be a loss of data related to the statuses like cycle time, time in status, etc. I would like to understand these consequences before making the change so I am not surprised with...
1
Will not implement
3
VOTE
Ability to map constants to custom fields in Github
Who would benefit? Anyone with a Github integration What impact would it make? Right now, the only way to prevent unhandled errors is to research the backend technical ID's and map those as constant values to send choice values over as a constant ...
1
Likely to implement
19
VOTE
8
VOTE
Allow for integrating Aha! Custom Tables to Rally
Currently custom tables cannot be integrated with Rally. In our environment we created a custom table to track Initiative Milestones and would like to integrate it with Rally Milestones, but that is not doable given the limitation.
0
Future consideration
15
VOTE
Allow for mapping to-dos in Asana integration
In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana.
An option to map To-dos to Tasks or Subtask would provide a ...
4
Future consideration
5
VOTE
21
VOTE
Tags should propagate bidirectionally into Pivotal Tracker
Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
2
Will not implement
12
VOTE
Synch story point estimates between Zenhub and Aha Epics (features)
We have linked Epics (Features) in Aha with Epics in Github Enterprise, and that is working fine. however we are using Zenhub to create story point estimates within Github, and would like to be able to reflect those estimates in Aha so we can do c...
4
Future consideration
21
VOTE
Support mapping JIRA Tempo Account field
When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
8
Unlikely to implement
5
VOTE
Project level automation with Jira
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved