ADD A NEW IDEA

Integrations

Showing 614

Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.

Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
Guest over 4 years ago in Azure DevOps Services and Server 2 Future consideration

Add API endpoint to capture configuration details (custom fields, layouts, etc.)

Useful for external visibility of configuration, change tracking, automated configuration of external integrations making use of the data, etc.
Guest over 4 years ago in Wanted 0 Future consideration

Limit amount of text that can be input in a custom field

Set a max for the amount of text that can be added in a custom field (i.e max 50 words)
Mary D over 4 years ago in Wanted 0 Future consideration

Pull in competitor information from Crunchbase

Reduce the tediousness of having to input competitor info manually
Guest over 4 years ago in Integrations 0 Future consideration

Change Button Click to Dropdown for Integration Screen

When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
Josh Tambor over 4 years ago in Jira 0 Future consideration

Features assuming the same release as its parent master feature when importing from Jira

Given that I have an epic in Jira, linked to a Master Feature in Aha And the Master Feature is found in "Release X", When I create a story beneath that epic in Jira, Then the story should be imported as a child to the Master Feature, AND assume ...
Guest over 4 years ago in Jira 0 Future consideration

Working with JIRA worklog dimension (worklog date)

Dear aha, in order to resolve reporting of time spent on features within specific timeframes, it might be useful to think about including worklog date of JIRA issues into synchronized aha backlogs. This would enable creation of reports where not o...
Daniel Pokrývka almost 5 years ago in Jira 0 Future consideration

Integrate Release Phase from Aha to Rally

Currently, the Aha to Rally Integration mapping does not include Release Phase. My suggestion is that Release Phase map to the Iteration field in Rally. This would greatly benefit anyone who uses both sides to not have to recreate the phase in eac...
Guest almost 5 years ago in Rally 0 Future consideration

Allow Feature or Master Feature to be pushed to Jira when the Aha! state is mapped but blocked when it is un-mapped

Our product management team wants to plan features prior to making the feature available via Jira Integration. For example while a feature is under consideration or in planning/grooming state it would only exists in Aha. Once the feature is ready ...
Guest almost 5 years ago in Jira 0 Future consideration

Have features push a status to a field in Jira when deleted

As a product manager I would like the ability to keep track of which items in JIRA/AHA have been deleted in each system. I know Aha! will not likely implement a feature to delete issues in Jira when respective items are deleted in Aha! However it ...
Guest almost 5 years ago in Jira 0 Future consideration