ADD A NEW IDEA

FILTER BY CATEGORY

Integrations

Showing 842

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Guest 4 days ago in Jira 2

Include Jira Dynamic Dates in API

When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...
Guest 6 days ago in Jira 0 Future consideration

Allow attachments to Feature comments to be integrated to Azure DevOps

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO.When yo...
Guest 6 days ago in Azure DevOps Services and Server 0 Future consideration

Add Closing Comment for Jira Integration

Our Jira environment has a requirement to enter a comment when "closing" a ticket. Aha does not have a place for this so if Aha! users close a feature in Aha, they will have to login to Jira and close it there as well. The request is to allow a "c...
Guest 7 days ago in Jira 0 Future consideration

Assign Integration to Specific User

Need the ability to assign a JIRA integration to a specific Aha! user instead of having each PM need to navigate to the integration and select Run As.
Yancey Larochelle-Williams 18 days ago in Jira 0 Future consideration

Add ability to sync custom table one to many field with AZURE DevOps Fields

I would like to be able to sync a one to many custom field, that links ties to a custom table, we have added to our requirements (PBIs), with the iteration path from DevOps. This does not appear to be possible.The reason for this is that we have c...
Jonathan Lewit 19 days ago in Azure DevOps Services and Server 0 Future consideration

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case:Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter 26 days ago in Jira 0 Future consideration

Notify users on Slack when they are tagged in Aha! through slack integration

Right now - when tagging someone in Aha! it links the user on Aha! to the comment e.g.Comment by XXX@YYY (link to user in Aha!) ....But it is useless to have it that way - it would be much nicer if the tagging on the comment in Aha! corresponded s...
Nir Soffer about 1 month ago in Slack 0 Future consideration

Trello integration set the unit for importing time units.

Currently, if you import time (estimates or progress) as a numeric field from Trello it comes in as minutes... forcing engineers (using Trello) to do estimates or track progress in minutes rather, then a configurable unit... hours, weeks, points ...
Jesse Stein about 1 month ago in Trello 0 Future consideration

Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe about 1 month ago in Jira 0 Future consideration