ADD A NEW IDEA

Integrations

Showing 919 of 8662

Add ability to map Custom Aha! Tables to Jira

Add the ability to map custom fields from custom tables in Aha! to Jira.
Guest almost 7 years ago in Jira 5 Future consideration

Create Aha! note from Slack message / thread

Who would benefit? everyone who uses slack and aha What impact would it make? reduce duplicated effort, improve knowledge management capture and record keeping How should it work? it should be possible to have a command to capture threads, slack c...
Guest 2 months ago in Slack 0 Planning to implement

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

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Stuart Blair 2 months ago in Azure DevOps Services and Server 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 over 8 years ago in Jira 10 Likely to implement

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