Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Problem

Unable to retrieve lingo id.

...

Info

Unable to retrieve lingo id for Default Notification Rule for Project with id '18475' com.botronsoft.jira.jiraservicedeskintegration.api.ServiceDeskIntegrationException: Unable to retrieve lingo id for Default Notification Rule for Project with id '18475' at com.botronsoft.jira.jiraservicedeskintegration.proxy.impl.CustomerNotificationSettingsProxyImpl40.retrieveLingoIdByLogicalId(CustomerNotificationSettingsProxyImpl40.java:391)

Solution

The error you are reporting indicates that there is a reference to a missing lingo in any of the default notification rules.

This could be impossible to trace in find the root cause from the UI, so better check in the database content of the following tables:FROM

  1. AO_C7F17E_LINGO

and

  1. AO_9B2E3B_THEN_ACT_CONF_DATA

The second will contain a row with CONFIG_DATA_KEY = "lingoLogicalId" which is not found in the column LOGICAL_ID of AO_C7F17E_LINGO.

...

Even after running query from this table "AO_C7F17E_LINGO" if it returns null for Logical_ID, then
you can check through the Jira UI if and which notification rules work, and if you actually need them. A potential solution is to delete the records from AO_9B2E3B_THEN_ACT_CONF_DATA and update the notification rules manually in Jira.In any case, we'd recommend to backup AO_9B2E3B_THEN_ACT_CONF_DATA first. backup AO_9B2E3B_THEN_ACT_CONF_DATA first.

Note

Before making any changes in the database like delete, update etc we suggest you to take the full backup of the database.

There is a little step-by-step guide that you can follow:

  • Delete the record in AO_9B2E3B_THEN_ACT_CONF_DATA that refers to the specific lingo (in this case '18475')

  • Clear caches from CMJ's Advanced page.

  • Run Integrity check and check if there are any errors.

...