Integrations
Sort by:
Trending
Status:
Unlikely to implement
Showing 947
3
VOTE
Do not show an update to the record description in History when sending a record to an integration
What is the challenge? When you send a record to an integration, the history incorrectly indicates that there was an update to the description. What is the impact? This can cause confusion about what changes were actually made. It also impacts tho...
0
Likely to implement
7
VOTE
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...
0
Planning to implement
3
VOTE
The ability to use an integration as a template prior to it's first time being enabled
What is the challenge? It's currently possible to use a disabled integration as a template, but before that is possible, you must first enable the integration and then disable it. What is the impact? This forces an extra step as users may want to ...
0
Future consideration
3
VOTE
Enabling the integration from the drop-down should allow integration to be used as a template
What is the challenge? If you use the drop-down menu to enable an integration versus the blue button at the bottom of the Enable tab on Integration settings, currently, it does not allow you to use that integration as a template. You must use the ...
0
Planning to implement
240
VOTE
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...
6
Future consideration
1
VOTE
10
VOTE
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...
1
Future consideration
175
VOTE
Dedicated Integration User
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 ...
16
Future consideration
1
VOTE
Add support for GitHub Issue Types
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...
0
Future consideration
12
VOTE
Calculate remaining effort based on detailed estimate and work done
What is the challenge? When adding a detailed estimate in Aha! or ADO and then logging actual effort via ADO, the Actual effort remaining value does not change and the progress bar total is inaccurate. Add initial estimate in aha! Send to ADO. Add...
2
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved