ADD A NEW IDEA

Integrations

Showing 948

JIRA Integration - Hide 'Send To' Options

Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder about 1 year ago in Jira 1 Future consideration

Apply "Update records" to a subset of records in an integration

The "Update records" function is very useful when Aha! Roadmaps becomes out of sync with my development tool- I can use it to bulk-update all of my linked records to make sure they are up to date with Jira. But, there is risk inherent in this kind...
Reilly O'Connor about 2 years ago in Integrations 0 Future consideration

better redmine integration - requirements are children of features, and tasks are children of requirements

redmine integration is very helpful and needed. "When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue." there should be a way of re...
Michael Martini almost 9 years ago in Integrations 0 Unlikely to implement

Azure DevOps integration support for designating default Iteration as backlog

Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
Ronnie Merkel over 4 years ago in Azure DevOps Services and Server 2 Future consideration

Create Feature Delivery Type field to map to Rally Feature

This field is required in Rally as it is used for Fixed Capacity Billing.
Guest over 4 years ago in Rally 0 Future consideration

Show JIRA # rather than Aha # on Roadmaps

JIRA came first at our company, and only a handful of users use Aha -- consequently, when I publish a roadmap, it is assumed that the issue numbers shown on the roadmap are JIRA issue numbers -- this creates a lot of confusion. I would like to be ...
Cameron O'Rourke almost 9 years ago in Jira 2 Unlikely to implement

Integrate Gliffy to enable editable flow diagrams in notes

I currently have to create flow diagrams outside of Aha and paste in a static version that others can not change. This is very restrictive and does not follow the collaborative flow I like to use. https://www.gliffy.com/
Guest almost 9 years ago in Wanted 3 Unlikely to implement

Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field

I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...
Stacy Monnahan about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Update mapped initiative field in integration when changing text of initiative name

The initiative field is available in the Jira integration under the Aha! feature record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the initiative record.) However, the mapped i...
Craig Pflumm over 4 years ago in Integrations 0 Future consideration

API endpoint for creating integration webhooks

I am building a bot for Aha. I want to go to a channel and say: > @aha subscribe PRODUCT_ID> This channel will now receive updates made to PRODUCT NAME On the backend, I want to create an activity webhook with a highly custom webhook URL. Ri...
Byrne Reese over 5 years ago in Integrations 1 Future consideration