On JIRA 5.1.3, my SOAP call can’t retrieve the ‘Phase’ field from issue JIRA-123. My trial code:
IssueService svc = SoapConnector.getIssueService();
CustomFieldService cfSvc = SoapConnector.getCustomFieldService();
Issue record = svc.findIssue("JIRA-123");
CustomField phaseField = cfSvc.lookupFieldByName("Phase");
Object phaseData = record.obtainField(phaseField);
Any advice?
I encountered a similar issue retrieving a custom field via SOAP on earlier JIRA versions. In my case, it turned out that the field wasn’t automatically populated in the SOAP response unless it was correctly mapped and accessible. I eventually verified that the field existed in the response record by inspecting all returned values. I was then forced to double-check the field name and its configuration within JIRA, as mismatches or access restrictions could prevent the value from being delivered. Ensuring proper mapping resolved the issue in my environment.
hey, ive seen similar issues before. your field may not make it thru the SOAP mapping properly due to config settings in jira. check if the field is public and correctly mapped in your soap setup. might be a version bug too, so a patch update could help.
In my experience, retrieving custom fields via SOAP on older Jira versions can be challenging due to differences between the internal field names used by the API and the names shown in the UI. I resolved a similar issue by experimenting with alternative field identifiers rather than just using the display name. Enabling extensive logging for the SOAP response helped me to inspect all fields available and identify the proper internal identifier. Adjusting the lookup accordingly proved effective and resolved the access problem to the custom field data.
Based on my experience, troubleshooting custom field retrieval in Jira SOAP web services requires verification on several fronts. When I faced a similar issue, I found that the custom field might be recognized differently in the SOAP API compared to the web UI. Although the field name seems straightforward, the internal identifier used by Jira could be different. I ended up checking the field configuration through admin settings and even attempted a direct API call to list available fields. This approach helped me to identify discrepancies between expected and actual field mappings, which once corrected, resolved the problem.
hey, i found using the direct field id worked better than the name. sometimes jira messes up the mapping. check your config and try with the raw id. it solved my issue!