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
about 1 month ago
in Jira
0
Likely to implement
Integrate Aha! and Confluence to link Confluence Pages in AHA! and transfer them with JIRA
Atlassian currently offers the ability to Integrate Confluence & Jira using Application Links which gives teams multiple features. https://confluence.atlassian.com/doc/use-jira-applications-and-confluence-together-427623543.html One of the fea...
Tyson Kretschmer
over 7 years ago
in Integrations
6
Future consideration
What is the challenge? We leverage Adobe Analytics for a lot of analytics and reporting. It would be great to have a direct non-third-party integration. What is the impact? Allowing for synergy between our goals and roadmaps in Aha! and our report...
Guest
13 days ago
in Integrations
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...
What is the challenge? There is no easy way to send ideas to engineering to work on or keep the information in sync. What is the impact? Time spent copy and pasting data. Out-of-date information leading to confusion. Describe your idea Like the re...
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
3 months ago
in Jira
0
Planning to implement
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
Integrate Github projects not associated with a repository
Currently the Github integration forces us to select a repository in order to integrate with a project but we have the need to integrate with projects that are not associated with repositories.
Guest
about 1 month ago
in GitHub
0
Future consideration
Currently the Jira integration doesn't allow users to map the custom release field, on records like features. We would like to be able to map this field and ideally to map it with a custom versions field in Jira. The two fields should be able to m...
Diane Metzger
about 1 month ago
in Jira
0
Future consideration
Add ability to set selected users for Slack notifications from Aha!
What is the challenge? Currently, the newest Aha! Slack integration does not allow you to set specific users to trigger a notification to Slack from Aha! in the way the previous version supported. What is the impact? You cannot filter down activit...
Stephanie Lechner
3 months ago
in Slack
3
Future consideration