Who would benefit? Product Managers What impact would it make? PdMs would benefit to have line-of-sight for updates that could impact them and their system of responsibility (“Copilot, tell me when the networking team will be upgrading their exter...
Guest
11 months ago
in Wanted
4
Future consideration
Who would benefit? Companies that leverage Viva Goals for OKR & initiative tracking in addition to Aha! Roadmaps What impact would it make? This would allow Product Managers and similar personas to continue the deep product-focused efforts in ...
David I.
11 months ago
in Integrations
2
Future consideration
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira
12 months ago
in Jira
0
Future consideration
Allow for Lookup Fields to be mapped in SFDC integration
Who would benefit? Everyone What impact would it make? Allows for further data collection from SFDC in Aha! How should it work? Similar to how other SFDC fields are currently mapped in today's configuration.
Guest
12 months ago
in Salesforce
0
Future consideration
Sync the change of parent link made in Aha! across 2 Azure DevOps integrations
Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest
12 months ago
in Jira
0
Future consideration
Allow project access token to be used instead of personal token for GitLab integration
Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
Guest
12 months ago
in Integrations
0
Future consideration
Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)
Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
Guest
12 months ago
in Integrations
0
Future consideration
Automatically update roll-up release name in integrations
Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
Nico Arias-Gonzalez
12 months ago
in Integrations / Jira
0
Future consideration
Who would benefit? anyone using Kanban and want's accurate process measurements What impact would it make? Better insights into the flow of work in your system, better forecasting of future work without having to ever ask for estimates that are mo...
Mike Lowery
12 months ago
in Wanted
0
Will not implement