Analyse Logs for Data Synchronisation

The error logs functionality in SimplifyQA is designed to help users identify and resolve issues encountered during the synchronization process between SimplifyQA and Jira. This feature provides detailed insights into errors, ensuring that users can troubleshoot and fix synchronization failures efficiently.

Purpose of Logs:

The error logs allow users to:

• Identify synchronisation issues: Understand why specific work items were not synced properly.

• Diagnose mapping problems: Pinpoint errors caused by incorrect or incomplete field mappings.

• Monitor real-time synchronisation failures: Access logs immediately after a failed sync attempt.

• Export logs for analysis: Download error details for in-depth troubleshooting.

When Error Logs are Generated?

Error logs are generated during synchronisation if:

• Fields between SimplifyQA and Jira are not properly mapped.

• Data in Jira does not match the expected values in SimplifyQA (e.g., missing or invalid values for mapped fields).

• The integration configuration between SimplifyQA and Jira encounters connectivity or API issues.

• Duplicate or conflicting data is detected during synchronisation.

How to View and Use Logs?

• Export Logs: Users can download the error logs by clicking on the logs icon.

• Understand Error Details: Each error log entry provides:

  • Issue Type: The type of work item that caused the error (e.g., STORY, TASK).

  • Error Description: A detailed explanation of the issue (e.g., "Field mapping is missing for the 'Status' field").

  • Timestamp: The date and time when the error occurred.

  • Affected Work Item ID: The unique identifier of the work item that encountered the error.

  Example Error:

  i. Issue Type: STORY

  ii. Error Description: "Field mapping for 'Priority' is not defined."

  iii. Timestamp: 2024-12-10, 10:45 AM

  iv. Work Item ID: SQA-1234

• Resolve Errors:

  • Refer to the error description to identify the root cause of the issue.

  • Update the field mappings or correct the problematic data in Jira.

  • Re-initiate the synchronisation process.