Integrations
Sort by:
Trending
Status:
Showing 945
19
VOTE
11
VOTE
Ability to see more than the last 200 logs in Aha-Jira Integrations
Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
2
Future consideration
7
VOTE
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
0
Future consideration
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
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
3
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
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
19
VOTE
Rally integration - Create and update dependency relationships between features as part of two-way integration
When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!
2
Future consideration
5
VOTE
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved