ADD A NEW IDEA

Integrations

Showing 631

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 2 months ago in Jira 0 Future consideration

Allow project access token to be used instead of personal token for GitLab integration

Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
Guest 2 months ago in Integrations 0 Future consideration

Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)

Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
Guest 2 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 over 6 years ago in Wanted 9 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), ea...
Guest over 4 years ago in Azure DevOps Services and Server 1 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair over 5 years ago in Azure DevOps Services and Server 9 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 almost 4 years ago in Integrations 3 Future consideration

Add Actionable Agile into your dev product

Who would benefit? anyone using Kanban and want's accurate process measurements What impact would it make? Better insights into the flow of work in your system, better forecasting of future work without having to ever ask for estimates that are mo...
Mike Lowery 2 months ago in Wanted 0 Future consideration

Figma Integration

We use Figma for UI mockups. It would be nice to have a Figma integration where I can quickly jump to or see the Figma mockup from/in Aha.
Guest over 1 year ago in Integrations 2 Future consideration

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black over 1 year ago in Jira 1 Future consideration