Work Item exchange between FastTrack & Polarion

[martin.schulze]

Hi!
I got a problem with editing Work Items in FastTrack. If I make any changes to a Work Item checked out of Polarion and save them, I wont see the Work Item in the Polarion web interface anymore after committing. It's caused by a change of the structure at the xml-file of the Work Item. The original order of fields gets absolutly confused. I will give you an easy example of a requirement.

original xml-Code like it was checked out of Polarion:

<?xml version="1.0" encoding="UTF-8"?>
<work-item>
<field id="created">2008-06-13 10:41:41.228 +0200</field>
<field id="title">R1.2</field>
<field id="severity">normal</field>
<field id="remainingEstimate">60h</field>
<field id="assignee">setools02</field>
<field id="priority">25.0</field>
<field id="linkedWorkItems">
<list>
<struct type="workitem">
<item id="suspect">false</item>
<item id="role">parent</item>
<item id="workItem">123456-1</item>
</struct>
</list>
</field>
<field id="type">requirement</field>
<field id="status">open</field>
<field id="description"/>
<field id="initialEstimate">60h</field>
<field id="author">setools01</field>
<field id="additional-Information" type="string"/>
<field id="test-criteria" type="string"/>
<field id="dependencies" type="string"/>
<field id="cost-of-realisation" type="string"/>
<field id="business-use" type="string"/>
<field id="target-definition-release" type="string"/>
<field id="contract-part" type="string"/>
<field id="source" type="string"/>
<field id="requirement-type" type="enum:requirement-type">projectspecific</field>
</work-item>

xml-Code after adding a comment and saving the Work Item:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<work-item>
<field id="initialEstimate">60h</field>
<field id="linkedWorkItems">
<list>
<struct type="workitem">
<item id="workItem">123456-1</item>
<item id="suspect">false</item>
<item id="role">parent</item>
</struct>
</list>
</field>
<field id="type">requirement</field>
<field id="author">setools01</field>
<field id="title">R1.2</field>
<field id="created">2008-06-13 10:41:41.228 +0200</field>
<field id="priority">25.0</field>
<field id="description"/>
<field id="remainingEstimate">60h</field>
<field id="status">open</field>
<field id="assignee">
<list>
<item>setools02</item>
</list>
</field>
<field id="severity">normal</field>
<field id="requirement-type" type="enum:requirement-type">projectspecific</field>
<field id="source" type="string"/>
<field id="contract-part" type="string"/>
<field id="target-definition-release" type="string"/>
<field id="business-use" type="string"/>
<field id="cost-of-realisation" type="string"/>
<field id="dependencies" type="string"/>
<field id="test-criteria" type="string"/>
<field id="additional-Information" type="string"/>
</work-item>

As you can see the structure of the xml-file completly changed.
And now the committed requirement is no longer visible at the Polarion web interface. (but of course it is visible at the SVN repository)
So how can I prevent this change of structure?

best regards!
martin.schulze

[martin.schulze]

resolved and closed.
It was a problem with different versions of Polarion. I used Polarion 2.6.5 with FastTrack 1.5
The problem disappeared, as I changed to Polarion 3.0.3

[NickEntin]

Hello,

as you probably noticed, we've announced relatively long ago discontinue of the version of FastTrack, you're discussing (the one, which works with XMLs directly).
We (and, of course, our customers) discovered major issues, especially scalability of FT with relatively big projects, field-level permissions issues, workflow inconsistencies, etc.
Therefore about a half of the year ago a new version of FastTrack was announced, this version now works remotely through WebServices with Polarion, ensuring consistent changes of the workitem, independency on amount, possibilities to work with workitems from LiveDocs or Modules, etc.
Unfortunately to the thread subject, I should admit that we'll not keep the old version maintained and we're not promising to keep structure of workitem.xml compatible to any versions of old FastTrack.

Best regards,
Nick