Skip Navigation LinksHome Page > Forums > SpiraTest Forums > SpiraTest Issues & Questi... > SpiraTeam synchornization...
We are currently seeing an error when synchronizing defects with JIRA on the resolution field. As JIRA does not store a physical resolution field for "Unresolved", the value being returned is empty. In JIRA, empty would mean "Unresolved" however JiraDataSync does not like this and throws the below error.
Is there a workaround to this to map any empty resolution fields to "Unresolved".
Error Inserting/Updating JIRA Issue IKEA-422 in SpiraTeam (Validation Fault: Custom_01=The field 'Resolution' requires a value. )
Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxError Inserting/Updating JIRA Issue XXX-422 in SpiraTeam (Validation Fault: Custom_01=The field 'Resolution' requires a value. )
Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object ins, Object outs, TimeSpan timeout)at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at : at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)at Inflectra.SpiraTest.PlugIns.Jira5DataSync.SpiraSoapService.ISoapService.Incident_Update(RemoteIncident remoteIncident)at Inflectra.SpiraTest.PlugIns.Jira5DataSync.DataSync.ProcessJiraIssueAsIncident(Int32 projectId, SoapServiceClient spiraImportExport, JiraIssue jiraIssue, List`1 newIncidentMappings, List`1 newReleaseMappings, List`1 oldReleaseMappings, Dictionary`2 customPropertyMappingList, Dictionary`2 customPropertyValueMappingList, RemoteCustomProperty incidentCustomProperties, RemoteDataMapping incidentMappings, String jiraProject, JiraManager jiraManager, String productName, RemoteDataMapping severityMappings, RemoteDataMapping priorityMappings, RemoteDataMapping statusMappings, RemoteDataMapping typeMappings, RemoteDataMapping userMappings, RemoteDataMapping releaseMappings, RemoteDataMapping incidentComponentMappings)
Please send this to our help desk as a ticket.
In general these kinds of issues relate to JIRA rejecting the incident because a required field ( Resolution ) is missing
This is a defect that existed in JIRA being synced into SpiraTeam, hence JIRA effectively has not rejected but SpiraTeam did because it is not expecting the resolution field to be empty. Unless that what you meant to say ?