What is the challenge? Data in Smartsheet "Contact List" Field cannot sync to Aha "Assign to User" Field, even if the user in available for selecting in the Assign to User field. Here are the error messages we saw Linking an Aha record with a S...

What is the challenge? When Smartsheet "Dropdown" field is configured with only "numbers" in the selection, Aha is not able to receive the Smartsheet value even if the dropdown value mapping is correctly set. Mapping Config For example: Tier (A...

What is the challenge? Existence of Smartsheet "system fields" cause error for the first time sending Aha record to Smartsheet, even if the system fields are not used in the mapping. System fields for example: Auto Number Created by Creat...

What is the challenge? Cannot select Smartsheet "Auto Number" field for mapping in the config page of Smartsheet integration. What is the impact? Impact: Medium (Workaround available but not ideal) Data in Smartsheet "Auto Number" field i...

What is the challenge? Formatted text in Aha "Note" field becomes html format in Smartsheet "Number/Text" field after sending the data through Smartsheet integration. For example: Aha Note field data This is an update from Aha Data received ...

We are currently using Aha! Roadmaps and asking for consideration of implementing OAuth authentication when setting up the integration to Azure DevOps Services. With Microsoft making the push towards strengthening their customers security posture,...

What is the challenge? We are using aha for the whole product lifecycle from discovery to delivery. However post delivery isn't tracked on aha for that 360 view of feature impact and progress towards goals and initiatives What is the impact?...

What is the challenge? Aha! currently supports Duo for two-factor authentication (2FA). However, many organizations standardize on other MFA providers such as Microsoft Authenticator, Okta Verify, or Google Authenticator. Relying solely on Duo c...

ADO integrations are sending to legacy domain "https://fredwin.visualstudio.com" instead of sending to "https://dev.azure.com/fredwin". Though the integration works as expected, clicking the link to the integrated record sends to the incorrect dom...

What is the challenge? Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot...