It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest
almost 8 years ago
in Integrations / Jira
16
Future consideration
Add 'Send to integration' automation action for Aha! Ideas <> Jira integration
What is the challenge? As PMs review ideas submitted to Aha! there may be ideas that need to be sent directly to Jira — thinking about bugs that are reported through an ideas portal. What is the impact? Those ideas need to be reviewed alongside al...
Justin Waldorf
2 months ago
in Ideas / Jira
0
Future consideration
Seamless Sync for Epics and Features Between Aha! and ADO when changing types
What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
Our Sales and Support teams use HubSpot CRM for all of their daily operations. I would love to have the same two-way sync that is provided for Salesforce within HubSpot. Essentially, the ability to associate contacts to ideas within HubSpot
Guest
almost 6 years ago
in Ideas / Integrations
18
Future consideration
Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to
What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...
Stephanie Lechner
3 months ago
in Jira
0
Likely to implement
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
Stephanie Lechner
5 months ago
in Jira
0
Planning to implement
What is the challenge? GitHub is introducing support for Issue Types In beta/previous mode currently https://docs.github.com/en/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization https://github.blog/ch...
Scott Vonderharr
3 months ago
in GitHub
0
Future consideration
Hi, would you consider integration with Miro, formerly RealTime Board? This is a great diagraming app, and has a good Jira integration which I was going to use in a convoluted way by pushing from Jira to Aha to get visibility back in Aha. In reali...
Guest
over 5 years ago
in Wanted / Whiteboards
18
Future consideration
Would be great if there was in integration into Monday.com. We have users in our organization that use this tool for managing their UI concepts and workload.
Kenny Burnham
almost 6 years ago
in Integrations
8
Future consideration
Update blank Jira fields on import to Aha! even if they are set up as a two-way sync
Currently only fields that are mapped one-way from Aha! to Jira will update when imported to Aha! - we import records from Jira to Aha! without a version set in Jira and Aha! automatically adds them to a default release in Aha! - we would like Aha...
Diane Metzger
23 days ago
in Integrations
0
Future consideration