ADD A NEW IDEA

Integrations

Showing 945

Trigger activity webhook event when a custom table field value is added or updated

Who would benefit? Users of the activity webhook would like to know when updates to custom table field values take place What impact would it make? How should it work? When a user updates or adds a value to a field within a custom table, that shou...
Will Lawrence 10 months ago in API / Integrations 0 Future consideration

Support bring your own LLM

Who would benefit? Customers who have build LLMs for their org who don't wis to use ChatGPT or have specific organisation context they wish to exploit What impact would it make? There are generative AI applications in Aha (and no doubt more planne...
Nigel Lawrence 10 months ago in Integrations 0 Future consideration

Integrate with ClickUp

Allow users to push information from Aha! into ClickUp and vice versa. A product roadmap/plan from Aha! could ideally be plugged directly into tasks in ClickUp. A project manager would then create their roadmaps in Aha! while the team works in th...
Guest about 7 years ago in Integrations 8 Unlikely to implement

Support updating JIRA Integration Links by csv upload

While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
Garret Duffy over 1 year ago in Jira 0 Future consideration

Change revision history descriptors for text field updates

It seems that some fields when updated via integration show a descriptor as XYZ changed integration link for Capability..123". This can be found in some values fields. Other fields like description simply state " XYZ updated the capability 123". T...
Karla Johnson about 2 years ago in Rally 1 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The int...
Matt Case over 8 years ago in Jira 13 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 almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

When using Import Records, not retaining parent/child relationship (AzDo Integration)

Who would benefit? Aha users when setting up a new workspace What impact would it make? Improves ability to only bring in needed records How should it work? After setting up integration mappings with parent/child relationships, have import records...
Guest 6 months ago in Integrations 1 Future consideration

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest over 5 years ago in Jira 5 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix ver...
Danny Archer almost 9 years ago in Jira 15 Future consideration