Share your product feedback

ADD A NEW IDEA

Integrations

Showing 945

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Guest almost 5 years ago in Account settings / Jira 1 Future consideration

Integration into Salesforce leads

We move customers from opportunity into lead generally before we can capture their ideas. They are then leads for their lifetime with our business. With the current Aha! Salesforce integration, we can't capture their ideas through Salesforce.
Melih Onvural over 8 years ago in Salesforce 3 Future consideration

Integration to Azure DevOps for teams capacity planning

We would like to use Points based capacity planning but it needs to be integrated with (in our case) Azure DevOps which is where the team is committed to and working on work. All of our Features and Master Features (Epics) in Aha are calculated ba...
Heath McCarthy over 4 years ago in Azure DevOps Services and Server 2 Future consideration

Allow for Delete of Jira Issue

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham over 5 years ago in Jira 2 Unlikely to implement

Automatically Update Records Converted in Jira

What is the challenge? Often times our Engineering counters in will convert stories/Spikes/Tasks to Epics in Jira What is the impact? We're not always told when these conversions happen and often have to do duplicate work to go into Aha! and conve...
Guest 7 months ago in Jira 0 Future consideration

Control how Estimates are converted and sent to TFS/VSTS

The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting. I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...
Guest over 6 years ago in Azure DevOps Services and Server 1 Future consideration

Choose the product on the integration with Zendesk

When you have multiple products in Zendesk it would be nice of you could select the product to link to by default, or change the order of the products in the drop down list. This prevents mistakes are made by the support agents.
Jeroen Geerbex over 9 years ago in Integrations 4 Future consideration

Don't Allow Jira Integration to Fail Based on One Field

What is the challenge? I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing w...
Guest 7 months ago in Jira 0 Future consideration

Integrate with http://phabricator.org

This is the open source ticketing tool that Facebook released.
Brian de Haaff about 10 years ago in Wanted 5 Unlikely to implement

Add more filters to integrations import

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer about 1 year ago in Jira 0 Already exists
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved