Integrations

Showing 945

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 Planning to implement

26 VOTE

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

5 VOTE

Improving handling when Jira users change issue type across record hierarchy

Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...

Stephanie Lechner about 1 year ago in Jira 0 Future consideration

35 VOTE

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 about 7 years ago in Wanted 9 Will not implement

14 VOTE

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 almost 3 years ago in Azure DevOps Services and Server 0 Future consideration

18 VOTE

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

1 VOTE

Add notification in Slack for Idea Created without having to specify category

What is the challenge? Currently the Slack integration doesn't have a notification type for just Created. It has a notification for Created by category and the user can technically use that and select Anything to get notifications for all ideas cr...

Peter Whisenant 3 months ago in Slack 0 Future consideration

3 VOTE

Prevent duplicate comments from importing into Aha!

What is the challenge? When re-syncing your integration from Settings -> Workspace-> Update records, duplicate comments can appear on the record in Aha! When a comment is edited in the inegration tool an additional comment with the edited co...

Gabrielle DeWitt 8 months ago in Integrations 1 Future consideration

6 VOTE

Keeping link to Jira when disable an integration

When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are ac...

Carina Velazquez about 1 year ago in Integrations 2 Future consideration

28 VOTE

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 almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY