ADD A NEW IDEA

Integrations

Showing 945

Better handling of when Features are removed from a Sprint

In our Aha / Azure DevOps integration we are mapping sprints back to Aha using a custom field, similar to this article: https://www.aha.io/support/roadmaps/integrations/azure-devops/sync-sprints-between-aha-and-azure-devops The issue seems to be t...
Dan Orth about 3 years ago in Azure DevOps Services and Server 0 Future consideration

Attachments linked to Note custom fields should be supported in Integrations 2.0

The note custom field allows for documents to be attached. However, when "attachments" are synchronized between Aha! and the development system, only attachments linked to the Description field are sent over. It would be ideal if the documents att...
Guest over 6 years ago in Jira 0 Future consideration

Slack integration should never show email address of anonymous idea submissions

My idea form allows users to submit ideas anonymously, and then it notifies our user community slack channel. This prompts great discussion and votes on good ideas. My problem is that even though someone submits the idea anonymously, the user’s em...
Guest over 6 years ago in Slack 0 Future consideration

Mockups, Axure Integration

For wireframes / mockups we are currently using Axure. It would be great to be able to use that instead of the Aha! build-in tool. When I think about it, your tool is rather a diagramming tool like LucidChart. To call it "mockup" is misleading in ...
Guest over 6 years ago in Wanted 1 Unlikely to implement

Synchornize workflow approvals from Aha! to Jira

Allow for mapping Aha! approvals to Jira via the integration. When a team member moves an item in Jira to a status that requires an approval in Aha!, pass the approval status back to Jira once it is updated in Aha!
Guest about 3 years ago in Jira 2 Future consideration

Many to one mapping for field integrations

The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
Jerimiah Rudden about 3 years ago in Jira 0 Future consideration

VSTS updating Aha! features base user stories

Leadership and executives are using Aha! more and more. Having the ability to represent the percentage completed of features in a given release is very important when reporting to large audience. I like to ability to show the percentage of the Fe...
Guest over 6 years ago in Azure DevOps Services and Server 0 Already exists

Integration last used field

To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.
Danielle A about 3 years ago in Jira 0 Future consideration

Ability to set defaults for Record Link

For nearly all Record link items we use Contains/Features. It would be great if we could set those by default. A hassle to always have to use the drop downs
Thomas Cruse over 6 years ago in Integrations 0 Future consideration

Pivotal Tracker: 2 way sync for Requirements — not just Features

Today PT can only update status in Aha for Features. We'd like to have it update the status of requirements as well. In our case, it's particularly useful because we map Aha Features to PT Epics (and Aha Requirements to PT Stories). So we're blin...
Yok Tan almost 10 years ago in Pivotal Tracker 2 Already exists