Hey everyone,
I’m having some issues with a new integration I set up between HP ALM and JIRA for syncing defects. The initial setup seemed fine. The integrity check passed and I enabled the sync. But when I try to actually sync the defects, I’m getting an error.
The error log shows it’s trying to create a new issue in JIRA, then refresh and update it. But then it hits a snag with this message:
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":{}}
After that, it looks like the connection to ALM gets dropped.
I’m pretty new to both ALM and JIRA, so I’m not sure what’s going wrong here. Has anyone run into this before or have any ideas what might be causing it? Thanks for any help!
I’ve encountered this issue before and believe it usually results from a mismatch in field mapping between ALM and JIRA. The error indicates that the payload is missing the expected ‘fields’ or ‘update’ information. From my experience, reviewing your configuration to ensure every mandatory and custom field in JIRA is properly mapped from ALM is essential. Also, verifying that you are using the correct API version and ensuring that no workflow conditions are interfering with issue creation can help resolve the problem.
I’ve dealt with a similar issue when setting up ALM-JIRA integration for our team. The error you’re seeing suggests there’s a problem with the field mapping between the two systems.
From my experience, this often happens when required fields in JIRA aren’t properly mapped to corresponding fields in ALM. Double-check your field mappings, especially for mandatory JIRA fields like ‘Summary’ and ‘Issue Type’.
Another thing to look out for is custom fields. If you have any custom fields in JIRA that are required for issue creation, make sure they’re included in the mapping.
Also, verify that the user account you’re using for the integration has the necessary permissions in both systems. Sometimes, permission issues can cause cryptic errors like this.
If none of that helps, I’d recommend enabling verbose logging on both sides if possible. It can provide more detailed error information that might point to the root cause.
Hope this helps! Let me know if you need any more specifics on troubleshooting steps.
yo, i’ve seen this before. it’s prolly a field mapping issue. check ur required fields in jira are matched up right with ALM. also, make sure ur integration user has the right permissions. if that dont work, try turning on debug logging for more info. good luck!