Troubleshooting ALM and JIRA Defect Synchronization

Hey everyone,

I’m having trouble with my ALM and JIRA integration. I set up a connection to sync defects from ALM to JIRA. The integrity check was fine, but when I try to sync, I get an error.

Here’s a snippet from the log:

05/22/2017,02:27:33,494 ERROR (Create.From1To2.Source-1) Create: Fatal exception caught,operation terminated. Cause: create: fatal error update: fatal error {"errorMessages":["one of 'fields' or 'update' required"],"errors":{}}

Does anyone know what this means? I’m pretty new to both ALM and JIRA. Any help would be awesome!

Thanks in advance!

From my experience with ALM-JIRA synchronization, this error typically occurs when the integration is missing crucial field mappings. The message suggests that either ‘fields’ or ‘update’ parameters are required but not provided in the sync configuration. I’d recommend reviewing your field mappings in the integration setup, particularly focusing on required JIRA fields like ‘Summary’ and ‘Issue Type’. Also, ensure that ALM defects contain valid data for all mapped fields. If the problem persists, checking the ALM and JIRA versions for compatibility and consulting their respective documentation for any known issues or recent changes could provide further insights.

hey there, i’ve seen this before. sounds like ur missing some required fields in the sync config. check ur field mappings, especially for stuff like summary and issue type in JIRA. make sure ALM defects have valid data for all mapped fields too. if ur still stuck, maybe look at version compatibility between ALM and JIRA. good luck!

I had a similar experience with ALM and JIRA integration where errors related to missing fields disrupted the sync process. In my case, the problem was that the connector was trying to create a JIRA issue without the necessary data. To resolve it, I spent some time double-checking the field mappings between ALM and JIRA and ensuring that every ALM defect provided valid values for the mandatory fields. Examining the JIRA API documentation also helped clarify the expected payload structure. A careful review of the configuration usually delivers valuable insights.