I've been successfully using the JIRA integration to move issues from JIRA to VersionOne. I recently tried to add a new JIRA filter from a different project (iI changed the configuration file to match), and I received the following error when trying to import the issues:
[INFO] 23-07-2012 10:31:52 Creating VersionOne Story for item from JIRA system with identifier WFSAND-5
[ERROR] 23-07-2012 10:31:52 Error during saving workitems: Value required: Story.Description
[ERROR] 23-07-2012 10:31:52 Error trying to create Workitem in VersionOne for [/WFSAND-5] Creation test in JIRA:
[ERROR] 23-07-2012 10:31:52 System.NullReferenceException: Object reference not set to an instance of an object. at VersionOne.ServiceHost.WorkitemServices.WorkitemWriterHostedService.Process Workitem(Object pubobj)
I get this error for all 8 issues in the filter.
Using SoapUI I called the getIssue web service and I can't find any difference in the XML returned for the issue that throws the error versus the issue that imports properly. Does anyone have some insight as to what web services the integration is calling so I can track down why this error is occurring?
Your log snippet indicates that VersionOne is having a problem creating the Story because Description has been marked as a required field. Generally, the out-of-the-box integrations don't work so well with required fields because the business rules must be consistent across 2 systems with different mechanisms for enforcing business rules. My recommendation is to relax that restriction.
That said, it's not the only option. I would start by checking to see if the JIRA issues in your new filter have descriptions. If they do, there could be a problem in parsing the descriptions for those issues. Does the integration user have adequate access to read them? From the Soap UI trace, do you see anything about the descriptions that might cause a problem (size, encoding, special characters)?
Ian Buchanan Product Manager for Platform and Integrations
On Wednesday, July 25, 2012 7:23:14 AM UTC-4, Joel wrote: > I've been successfully using the JIRA integration to move issues from JIRA > to VersionOne. I recently tried to add a new JIRA filter from a different > project (iI changed the configuration file to match), and I received the > following error when trying to import the issues:
> [INFO] 23-07-2012 10:31:52 Creating VersionOne Story for item from JIRA > system with identifier WFSAND-5
> [ERROR] 23-07-2012 10:31:52 Error during saving workitems: Value required: > Story.Description
> [ERROR] 23-07-2012 10:31:52 Error trying to create Workitem in VersionOne > for [/WFSAND-5] Creation test in JIRA:
> [ERROR] 23-07-2012 10:31:52 System.NullReferenceException: Object > reference not set to an instance of an object. at > VersionOne.ServiceHost.WorkitemServices.WorkitemWriterHostedService.Process Workitem(Object > pubobj)
> I get this error for all 8 issues in the filter.
> Using SoapUI I called the getIssue web service and I can't find any > difference in the XML returned for the issue that throws the error versus > the issue that imports properly. Does anyone have some insight as to what > web services the integration is calling so I can track down why this error > is occurring?
I simplified the filter and am pulling up two test cases that have basic information in them. When I restarted the integration I received a new error message:
[INFO] 25-07-2012 16:23:28 Creating VersionOne Story for item from JIRA system with identifier WFSAND-7 [ERROR] 25-07-2012 16:23:29 Error during saving workitems: Violation'Required'AttributeDefinition'Super'Story: NULL [ERROR] 25-07-2012 16:23:29 Error trying to create Workitem in VersionOne for [/WFSAND-7] Test Story 1 in JIRA: [ERROR] 25-07-2012 16:23:29 System.NullReferenceException: Object reference not set to an instance of an object. at VersionOne.ServiceHost.WorkitemServices.WorkitemWriterHostedService.Process Workitem(Object pubobj)
I'm assuming that this is on the VersionOne side where there is a NULL value. Is there any documentation that shows the mappings between JIRA and VersionOne that the integration is expecting to see? Can we see this in the source code that's available on the web site?
On Wednesday, July 25, 2012 9:19:39 AM UTC-4, ibuchanan wrote:
> Joel,
> Your log snippet indicates that VersionOne is having a problem creating > the Story because Description has been marked as a required field. > Generally, the out-of-the-box integrations don't work so well with required > fields because the business rules must be consistent across 2 systems with > different mechanisms for enforcing business rules. My recommendation is to > relax that restriction.
> That said, it's not the only option. I would start by checking to see if > the JIRA issues in your new filter have descriptions. If they do, there > could be a problem in parsing the descriptions for those issues. Does the > integration user have adequate access to read them? From the Soap UI trace, > do you see anything about the descriptions that might cause a problem > (size, encoding, special characters)?
> Ian Buchanan > Product Manager for Platform and Integrations
> On Wednesday, July 25, 2012 7:23:14 AM UTC-4, Joel wrote:
>> I've been successfully using the JIRA integration to move issues from >> JIRA to VersionOne. I recently tried to add a new JIRA filter from a >> different project (iI changed the configuration file to match), and I >> received the following error when trying to import the issues:
>> [INFO] 23-07-2012 10:31:52 Creating VersionOne Story for item from JIRA >> system with identifier WFSAND-5
>> [ERROR] 23-07-2012 10:31:52 Error during saving workitems: Value >> required: Story.Description
>> [ERROR] 23-07-2012 10:31:52 Error trying to create Workitem in VersionOne >> for [/WFSAND-5] Creation test in JIRA:
>> [ERROR] 23-07-2012 10:31:52 System.NullReferenceException: Object >> reference not set to an instance of an object. at >> VersionOne.ServiceHost.WorkitemServices.WorkitemWriterHostedService.Process Workitem(Object >> pubobj)
>> I get this error for all 8 issues in the filter.
>> Using SoapUI I called the getIssue web service and I can't find any >> difference in the XML returned for the issue that throws the error versus >> the issue that imports properly. Does anyone have some insight as to what >> web services the integration is calling so I can track down why this error >> is occurring?
The error is similar to what you were seeing before. This time, instead of the integration failing on a blank description, it's failing because the "Super" relationship has been made required (it's called "Epic" in the user interface). To be clear, neither Description nor Super/Epic are required by default so someone has made them required fields, either globally or for a project workspace that affects your target project. Although you might work-around the required Description field, the out-of-the-box JIRA integration knows nothing of Epics so it will never be able to satisfy the required Super/Epic relationship. Again, I don't recommend using required fields with any of our integrations.
In re-reading this thread, I wonder if I overlooked something in your original post. You said the integration was working and you were creating a new filter for a new JIRA project. That might be a source of trouble. If you just wanted to extend the integration to a new JIRA project, then you shouldn't use a new filter. Just extend the other filter to include items from multiple projects. If the JIRA project name matches a project name in VersionOne, then you don't need to do anything -- the integration will match up the names and put the Defects into the right project. Otherwise, use the ServiceHostConfigTool.exe to add a project mapping for each JIRA project to the right VersionOne project. In other words, you only need a new JIRA filter if you want some JIRA issues mapped to Stories and others mapped to Defects.
To answer your final questions more directly, the only fields that are mapped are Name, Description, and Parent (Project). The Name and Description come directly from JIRA. The Project is either a configured mapping or "guessed" based on name. You are welcome to read the source code, or even use it as a starting point for more sophisticated integration. From what I can tell, your problem isn't in the mapping of these fields from JIRA but in the rules applied to them in the VersionOne configuration. The place to look is in VersionOne Administration -> Display Fields -> Story.
On Wednesday, July 25, 2012 5:30:28 PM UTC-4, Joel wrote: > Ian,
> I simplified the filter and am pulling up two test cases that have basic > information in them. When I restarted the integration I received a new > error message:
> [INFO] 25-07-2012 16:23:28 Creating VersionOne Story for item from JIRA > system with identifier WFSAND-7 > [ERROR] 25-07-2012 16:23:29 Error during saving workitems: > Violation'Required'AttributeDefinition'Super'Story: NULL > [ERROR] 25-07-2012 16:23:29 Error trying to create Workitem in VersionOne > for [/WFSAND-7] Test Story 1 in JIRA: > [ERROR] 25-07-2012 16:23:29 System.NullReferenceException: Object > reference not set to an instance of an object. > at > VersionOne.ServiceHost.WorkitemServices.WorkitemWriterHostedService.Process Workitem(Object > pubobj)
> I'm assuming that this is on the VersionOne side where there is a NULL > value. Is there any documentation that shows the mappings between JIRA and > VersionOne that the integration is expecting to see? Can we see this in > the source code that's available on the web site?
> Thanks,
> --Joel
> On Wednesday, July 25, 2012 9:19:39 AM UTC-4, ibuchanan wrote:
>> Joel,
>> Your log snippet indicates that VersionOne is having a problem creating >> the Story because Description has been marked as a required field. >> Generally, the out-of-the-box integrations don't work so well with required >> fields because the business rules must be consistent across 2 systems with >> different mechanisms for enforcing business rules. My recommendation is to >> relax that restriction.
>> That said, it's not the only option. I would start by checking to see if >> the JIRA issues in your new filter have descriptions. If they do, there >> could be a problem in parsing the descriptions for those issues. Does the >> integration user have adequate access to read them? From the Soap UI trace, >> do you see anything about the descriptions that might cause a problem >> (size, encoding, special characters)?
>> Ian Buchanan >> Product Manager for Platform and Integrations
>> On Wednesday, July 25, 2012 7:23:14 AM UTC-4, Joel wrote:
>>> I've been successfully using the JIRA integration to move issues from >>> JIRA to VersionOne. I recently tried to add a new JIRA filter from a >>> different project (iI changed the configuration file to match), and I >>> received the following error when trying to import the issues:
>>> [INFO] 23-07-2012 10:31:52 Creating VersionOne Story for item from JIRA >>> system with identifier WFSAND-5
>>> [ERROR] 23-07-2012 10:31:52 Error during saving workitems: Value >>> required: Story.Description
>>> [ERROR] 23-07-2012 10:31:52 Error trying to create Workitem in >>> VersionOne for [/WFSAND-5] Creation test in JIRA:
>>> [ERROR] 23-07-2012 10:31:52 System.NullReferenceException: Object >>> reference not set to an instance of an object. at >>> VersionOne.ServiceHost.WorkitemServices.WorkitemWriterHostedService.Process Workitem(Object >>> pubobj)
>>> I get this error for all 8 issues in the filter.
>>> Using SoapUI I called the getIssue web service and I can't find any >>> difference in the XML returned for the issue that throws the error versus >>> the issue that imports properly. Does anyone have some insight as to what >>> web services the integration is calling so I can track down why this error >>> is occurring?
Thanks to your help, I've resolved this issue. For some reason the description and story fields became required in VersionOne. What was interesting about this is that when I first looked at Display Fields at a global level they were unchecked. When I turned on Project Workspace (previously disabled) and went to the individual project, I saw that both those fields were checked. Once I turned them off the import worked fine.
