Integrations
Sort by:
Trending
Status:
Future consideration
Showing 946
2
VOTE
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...
0
Future consideration
2
VOTE
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...
0
Future consideration
1
VOTE
Better inform users in situations with records linked inside disabled integrations
It is currently possible to link an Aha! record to an existing record in the development system. However, it is not possible to link to an existing Aha! record that is already linked with another record in the integrated system. It would be helpfu...
0
Future consideration
1
VOTE
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...
0
Future consideration
2
VOTE
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 ...
1
Unlikely to implement
2
VOTE
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...
0
Already exists
1
VOTE
2
VOTE
1
VOTE
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...
0
Future consideration
3
VOTE
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...
2
Already exists
© 2024 Aha! Labs Inc.•All rights reserved