Integrations
Sort by:
Trending
Status:
Future consideration
Showing 604
9
VOTE
Allow requirements to be associated with the release record
The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
0
Future consideration
5
VOTE
Allow the use of "Integration" fields in Report calculated field formulas
Currently, integration fields like "Rally formatted_id" cannot be used within a formula for report calculated fields. This is limiting since it means we need to create a custom field to be based on these fields to use within the formulas. Consider...
0
Future consideration
8
VOTE
Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories
I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!.
We'd much prefer that this not be the ca...
1
Future consideration
1
VOTE
Support configuring capacity units of time for ADO server integrations
What is the challenge? Currently the "Configure" option to select units of time to send estimates to ADO is only avaiable on the ADO Services integration and is not available for users using the Server integrations. What is the impact? Users are u...
0
Future consideration
8
VOTE
7
VOTE
10
VOTE
Integrate Aha Program Increment (PI) custom field with Rally Release field
Today in Rally, following an orthodox SAFe Portfolio model, we organize our work based on Product Increment (PI) intervals that include four(4) two week sprints and on two week sprint for Innovation and planning. Every ten weeks we hold another PI...
0
Future consideration
10
VOTE
Ability to view the specific development integration that an object is using
There are a few instances when it would be valuable to report on the name of the integration that an object is using to connect with an external development system.
This would help to identify when integrations are being 'cut over' in order to tra...
1
Future consideration
9
VOTE
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
1
Future consideration
7
VOTE
Allow linking of Features and Releases to a specific DevOps Iteration Level
We use a more granular structure to the Iterations in DevOps so mapping items to just the top level is not really suitable to keep a feature synchronized correctly and could involve a lot of manual changes at the beginning and end of a release. Fo...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved