Redmine integration - Configuration help (quick & dirty)

[fman]

<attribute></attributes> Why ?
on XML config on TestLink provide direct access to a minimun set of MANDATORY attributes => without it issue can not be created.
After first development/release of this feature people that knows better Redmine start asking for other attributes.
Then to manage this other set of unknown attributes in a generic way idea was loop over an object property and blidly add it to request.
Drawback/limitations
I can not manage type (because I do not request this info) => will treat always as STRING
* Special case Target Version
http://www.redmine.org/issues/6843
"Target version" is the new display name for this property,
but it's still named fixed_version internally and thus in the API.

[fman]

Working example on local redmine installation (teslink & redmine on same host)
CRITIC:
In order to be able to SET parent_issue_id the API KEY used has to belong to an user that has RIGHT to do this.
<issuetracker>
<apikey>81538efac88d05a1dbf77b80e793526dbd4921dd</apikey>
<uribase>https://localhost:8443/redmine/</uribase>
<uriview>https://localhost:8443/redmine/issues/</uriview>
<projectidentifier>main-02</projectidentifier>
<attributes>
<targetversion>1</targetversion>
<parent_issue_id>20</parent_issue_id>
</attributes>
</issuetracker>