Redmine integration - Configuration help (quick & dirty)
Posted: Sun Aug 17, 2014 8:12 am
<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.
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.