|Anonymous | Login | Signup for a new account||2019-02-15 22:11 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004218||TestLink||Export/Import||public||2011-02-03 01:31||2014-04-25 17:39|
|Platform||X86||OS||Linux||OS Version||XUbuntu 9.4|
|Product Version||1.9.1 (bug fixing)|
|Fixed in Version||1.9.10 (2014 Q1 - bug fixing)|
|Summary||0004218: Import of Custom Fields Failing due to spaces...|
|Description||I have an import file that was run though tidy (html tidy in XML mode) and when I attempted to import it, the custom fields would not import. The problem is how the import function is processing spaces. This problem seems to impact only the custom fields, not the main fields, so I hope it is a simple fix.|
|Steps To Reproduce||Create file with defined custom fields that are "tidy"|
<custom_fields> <custom_field> <name> <![CDATA[QATrackSuiteID]]> </name> <value> <![CDATA[TSC462-0.2]]> </value> </custom_field> </custom_fields>
The same data will import correctly if the fields are as follows:
<custom_fields> <custom_field> <name><![CDATA[QATrackSuiteID]]></name> <value><![CDATA[TSC462-0.2]]></value> </custom_field> </custom_fields>
|Tags||No tags attached.|
|QA Team - Task Workflow Status||READY FOR TESTING|
|Attached Files|| ragged_file2.xml [^] (349 bytes) 2011-02-05 15:38|
testcase-192-1-ragged.xml [^] (1,087 bytes) 2011-02-06 08:50
Case-0004218-SampleData.zip [^] (2,591 bytes) 2011-02-07 17:51
1. please avoid use of elipsis on issue subject
2. Can you explain what you spaces are talking about in addition to put the example and leave to us the task of try to understans what is happening .
3. you can contribute with the fix if you want
4. attach BOTH XML files instead of pasting on note, this way we can do same test done by you.
1. creating a file with content provided result in a problem when trying to import Custom Field definition due to missing required values.
2. We need detailed steps to reproduce in order to assign to out task list.
|Tested Custom Field import definition using attached file -> no issues|
My apologies. I am new to this project, and am not a PHP developer. I have obviously picked up some ticket habits from our work environment that do not conform to this community's conventions.
I am attaching a set of files that should demonstrate the issue. I included snippets because I can not deliver the actual XML files we are using. For these samples, I have sanitized a small fragment to show the issue. I am also including an export of the custom fields that have been defined, and an error file 'error_responses.txt'
The issue is simply that the import is reading a space before and after the CDATA sections, and is therefore unable to identify to match the custom field name, since the custom field does not have the spaces. It does not appear that this problem exists for standard fields, though I have not done any extensive testing to check.
|ok, thanks for samples|
|2011-02-03 01:31||bjramsey||New Issue|
|2011-02-04 11:46||fman||Note Added: 0013509|
|2011-02-05 15:04||fman||Note Added: 0013521|
|2011-02-05 15:38||fman||Note Added: 0013522|
|2011-02-05 15:38||fman||File Added: ragged_file2.xml|
|2011-02-05 16:09||fman||Assigned To||=> fman|
|2011-02-05 16:09||fman||Status||new => feedback|
|2011-02-06 08:50||fman||File Added: testcase-192-1-ragged.xml|
|2011-02-07 17:50||bjramsey||Note Added: 0013554|
|2011-02-07 17:50||bjramsey||Status||feedback => assigned|
|2011-02-07 17:51||bjramsey||File Added: Case-0004218-SampleData.zip|
|2011-02-08 20:42||fman||Note Added: 0013571|
|2013-12-30 14:42||fman||QA Team - Task Workflow Status||=> READY FOR TESTING|
|2013-12-30 14:42||fman||Status||assigned => resolved|
|2013-12-30 14:42||fman||Fixed in Version||=> 1.9.10 (2014 Q1 - bug fixing)|
|2013-12-30 14:42||fman||Resolution||open => fixed|
|2013-12-30 14:42||fman||Relationship added||child of 0006048|
|2014-04-25 17:39||fman||Note Added: 0020864|
|2014-04-25 17:39||fman||Status||resolved => closed|
|Copyright © 2000 - 2019 MantisBT Team|