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 9 years ago
in Integrations / Jira
16
Future consideration
Add ability to restrict auto import of parent record with ADO
What is the challenge?
When importing features from ADO the parent epic is automatically brought into Aha! Epics can live in separate projects and the team does not always want them to display within Aha!
What is the impact?
Difficulty in ...
Unable to map 'Assigned To User' of aha to 'Assigned To' field of ADO due is domain mismatch
What is the challenge?
Our organization has transitioned recently and so we got new domain for employees, currently both the domains are valid for employees. In few application like Aha! we have old domain itself, but in the new applications we ...
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
Ability to map editable choice lists in Aha! with the Jira Team field and support bi-directional sync
What is the challenge?
Bi-directional sync of the Jira team field is only supported for some Aha! custom fields
What is the impact?
Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...
Deepti Pradeep
about 2 months ago
in Jira
1
Future consideration
Azure DevOps Integration - Sync dependencies at UserStories/Requirements level
What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
What is the challenge? When statuses are mapped as bi-directional in integrations (Jira etc.) - transitioning rapidly between statuses in a fixed workflow in Aha! does not send each transition to the dev tool. With a fixed workflow in the dev tool...
Jeanette Resnikoff
9 months ago
in Jira
2
Future consideration
What is the challenge? GitHub is introducing support for Issue Types In beta/preview mode currently https://docs.github.com/en/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization https://github.blog/cha...
Scott Vonderharr
about 1 year ago
in GitHub
1
Likely to implement
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
over 6 years ago
in Integrations
10
Future consideration
What is the challenge?
Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description.
What is the impact?
This leads to significant data loss — important contextual information, formatting, or...