ADD A NEW IDEA

Integrations

Showing 945

Integrations 2.0: Add dependency link to connect records without natural relationships together

In integrations 1.0 if I mappedFeatures = StoryRequirement = TaskAha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other.In 2...
Danny Archer over 6 years ago in Dependencies / Jira 3 Future consideration

Enable tags to be a selection for Azure DevOps integration of requirements

What is the challenge? You can sync tags for features but not requirements, What is the impact? creates duplication of work having to recreate tags in Azure DevOps Describe your idea As part of the field mapping for Azure DevOps integration "tags"...
Guest 4 months ago in Azure DevOps Services and Server 0 Future consideration

Including Attachments from Comments for Jira Integration

It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
Reut Levi over 4 years ago in Integrations 3 Future consideration

Add support to map Azure Boolean Fields to Aha

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...
Jerrold Emery over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations

With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations. This makes scaling integrations simple as after the first setup, a user never has to add another webhook. With Azure DevOps (TFS), each i...
Guest about 5 years ago in Azure DevOps Services and Server 1 Future consideration

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox over 3 years ago in Jira 0 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer about 9 years ago in Jira 12 Likely to implement

Please add worksheet field in mapping of aha! JIRA integration configuration.

Who would benefit? What impact would it make? We can integrate worksheet field with JIRA. How should it work?
Guest 7 months ago in Integrations 0 Future consideration

Clubhouse integration

Clubhouse is gaining a full head of steam and being adopted widely as a replacement for Trello and Jira - it strikes a great balance between the two. We're currently evaluating a move from PivotalTracker to Clubhouse, and while we're excited by th...
Guest almost 7 years ago in Wanted 9 Future consideration

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush about 1 year ago in Jira 0 Future consideration