SpiraTeam synchornization issue with resolution status "unresolved" from JIRA

Wednesday, September 19, 2018 2:44:08 PM

Hi,

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, Prox
Error 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 [0]: 
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)

 

Thanks,

Kevin.

2 Replies
Wednesday, September 19, 2018 3:07:06 PM
Avatar
re: kevin.mavely on Wednesday, September 19, 2018 2:44:08 PM

Hi Kevin,

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

Regards

Adam

Wednesday, September 19, 2018 3:12:46 PM
Avatar
re: inflectra.adam on Wednesday, September 19, 2018

Hi Adam,

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 ?

Thanks,

Kevin.

Statistics
  • Started: Wednesday, September 19, 2018 2:44:08 PM
  • Last Reply: Wednesday, September 19, 2018 3:12:46 PM
  • Replies: 2
  • Views: 111