Error syncing defects between HPE ALM and JIRA - fields or update required

I’m trying to set up synchronization between HPE ALM and JIRA for defect tracking. The connection test was successful and the integrity validation passed without issues. However, when I attempt to run the actual sync process, I keep running into an error.

The sync starts normally and creates new issues in JIRA, but then fails during the update phase. Here’s what I see in the logs:

05/22/2017,02:27:31,654 INFO Creating new JIRA issue
05/22/2017,02:27:32,874 INFO Refreshing issue id:26906
05/22/2017,02:27:32,925 INFO Updating issue id:26906
05/22/2017,02:27:33,494 ERROR Fatal exception: create and update failed
Error details: {"errorMessages":["one of 'fields' or 'update' required"],"errors":{}}
05/22/2017,02:27:33,499 INFO Disconnecting HPE-ALM adapter

The error message mentions that either ‘fields’ or ‘update’ is required, but I’m not sure what this means in the context of ALM-JIRA integration. I’m fairly new to working with both tools, so any guidance on what might be causing this issue would be really helpful. Has anyone encountered this type of sync error before?

Had this exact problem when we set up ALM-JIRA sync last year. It’s happening because the REST API call to JIRA has a malformed payload structure. I found our sync adapter was sending empty update requests without field definitions. Check your field mapping in the synchronizer settings - make sure all required JIRA fields are mapped to ALM fields. Also verify your JIRA project workflow actually allows updates to those fields. We had to add default values for mandatory fields that ALM wasn’t populating. Fixed the field mappings and sync worked perfectly.

seems like u might not have all the fields set in ur JIRA API call. this error pops up when field mapping aint right. make sure all mandatory JIRA fields are linked properly from ALM.

I hit this same issue during our migration. The synchronizer’s trying to update a JIRA issue but the request payload is messed up or missing data. Usually happens when the sync tool attempts an update without specifying which fields to change or how to change them. Check your synchronizer config - make sure it has proper permissions for field updates in JIRA. Sometimes initial creation works fine but updates fail because the sync service account can’t edit certain fields. Also check if any custom fields in your JIRA workflow became mandatory after you set up the initial sync. The synchronizer might be trying to update records without providing values for those newly required fields.