Aha! Roadmaps | How to diagnose development tool integration log messages

The integration between Aha! Roadmaps and your development tool manages a massive amount of details and realtime updates. Most of the time, it keeps everything in sync between the two tools perfectly. If you run into trouble, your first step should be to check the integration log messages.

In this article, we will walk through common log messages you might see, with brief explanations and recommended actions for you to take.

Click any of the following links to skip ahead:

Access integration logs
Info
Warning
Error

Access integration logs

You can view integration logs in three places:

Settings ⚙️ Integration updates for all integration updates in your Aha! Roadmaps account.
Settings ⚙️ Account Integrations for account-level integrations.
Settings ⚙️ Workspace Integrations for workspace-level integrations.

Since development tools are workspace-level integrations, head to Settings ⚙️ Workspace Integrations and click on the integration whose logs you want to access. Then click View log messages at the bottom of the page.

Log messages come in three types:

Red | Error: Red error logs indicate that something in the integration failed. They are often preceded by an amber warning that offers a more technical description of the issue, which can be helpful for understanding the reason for the failure. For example, a red error log may be logged if you do not allow list the Aha! Roadmaps IP addresses and Aha! Roadmaps cannot contact your server.
Amber | Warning: Amber warning logs indicate something happened that may be unexpected but is not necessarily a problem. Warnings can provide reasons for an error or offer additional background to help you troubleshoot an issue.
Blue | Information: Info logs display a record of integration activity, such as receiving a webhook.

In the following sections, we will discuss example messages you might see in your logs for each of these types.

Top

Info

Log message	Explanation	Action
Skip creating candidate for XXXX as feature due to service restriction	The record has been created in your Aha! account, and therefore will not be imported from your development tool.	If you wanted to import the record from your development tool, search for the record in your Aha! account to make sure it does not already exist there. If it does not, you can create a record in Aha! and use the Link to existing option to connect it to that development tool record.
Skip creating candidate for XXXX due to parent being in other product	Requirements in Aha! Roadmaps cannot be imported as standalone records. They need to be linked to a parent feature. When a requirement comes in from a development tool, the integration checks to see if the parent feature exists. In this case, the feature exists in another Aha! Roadmaps workspace linked to another development tool integration. Since requirements have to exist in the same Aha! Roadmaps workspace as their parent feature, the integration has skipped creating the requirement in this workspace.	Ignore
Skipping update updated XXXX YYYY [aggregate_timeestimate, aggregate_work_done, aggregate_timeoriginalestimate, progress_children, display_short, display_summary, display_display, display_link], used by another integration	The development tool record you are trying to update is already integrated with Aha! Roadmaps through another active integration configuration. Since that other integration is responsible for updating this record, no changes have been made through your current integration update.	Ignore
Applying inverse update to [Record type] [Mapped fields]	When you map fields between Aha! Roadmaps and a development tool, you can choose one of several mapping directions. If you import records from a development tool into Aha! Roadmaps, Aha! Roadmaps will then send to the development tool any fields that have a One way (set once) mapping direction from Aha! Roadmaps to a development tool.	Ignore

Top

Warning

Log message

Explanation

Action

The property aha does not exist

The aha property indicates that a record was created in your Aha! account and then sent to the development tool. Records created in the development tool do not have this property.

The purpose of the aha property is to help in the event that it is important to understand which application the record was created in. You can safely ignore the warning message since there is no problem with the integrated record.

Ignore

Received change updated XXXX YYYY [status, customfield_#####, display_short, display_summary, display_display, display_link] but found no mappings

Updates were made in the development tool to a record that is linked to an Aha! Roadmaps record. But since the development tool fields that were updated are not mapped to any Aha! Roadmaps field, no changes were made to the linked Aha! Roadmaps record.

Ignore

Top

Error

Log message

Explanation

Action

[Record] cannot be imported as a requirement because there is no valid relationship link to an Aha! feature

Requirements in Aha! Roadmaps cannot be imported as standalone records. They need to be linked to a parent feature. When you link Aha! and development tool types together, you need to include a parent link between the analog to Aha! requirements and the analog to Aha! features.

We have recommendations for record mapping for Jira and Azure DevOps

In Aha! Roadmaps, navigate to the Mappings step of your integration configuration, then follow these instructions to establish parent-child record links.
Save your updated integration configuration and re-run the record import.

No valid transition to status ### for issue XXXX

Workflows in your development tool often need transitions between workflow statuses.

This error occurs when an integration is attempting to move a record in your development tool into a status that would require skipping a step in the workflow.

If you think the status transition is appropriate and you have appropriate user permissions in your development tool, add a workflow status transition between the original and intended status.

Top

If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.