Integrations
Sort by:
Trending
Filter by:
Status
Showing 986 of 9701
13
VOTE
Expose scorecard metrics as integration fields
Currently, scorecard metrics do not appear to be available to integrations. We would like to represent these components in our development system in the interest of transparency to our development teams, but there is no way to get this data across...
3
Future consideration
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
Future consideration
12
VOTE
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...
3
Future consideration
7
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
14
VOTE
Auto Resend all Fields per release
Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
2
Future consideration
17
VOTE
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
2
VOTE
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved