Forums | Users |
Search | Signup | Login

fields_string doesn't work, and neither hours_actual nor percentage_complete actually display

Subscribe to fields_string doesn't work, and neither hours_actual nor percentage_complete actually display 3 post(s), 2 voice(s)

 
Avatar Steven Merrill 5 post(s)

The body should more or less say it all – I’m trying to construct a dynamic report, and conditions_string works fine, but neither fields_string (via query string) or fields-string (via XML request) are respected.

In addition, none of my TicketReports are coming back with the hours_actual or percentage_complete fields in them.

I’m trying to build an automated burndown chart utility for our project, and without being able to get hours_actual, there will be no way to do it.

Samples of what doesn’t work:

curl -i -u “user:pass” -X GET -H ‘Accept: application/xml’ -d ‘<request><title>A Dynamic Report</title><conditions-string>version-eq-33441</conditions-string><fields-string>number,summary,hours_estimate_current,hours_actual</fields-string></request>’ http://{mydomain}.unfuddle.com/api/v1/projects/{id}/ticket_reports/dynamic

The condition is applied, but only the default fields (sans hour or percentage) are displayed.

curl -i -u “user:pass” -X GET -H ‘Accept: application/xml’ ‘http://{mydomain}.unfuddle.com/api/v1/projects/{id}/ticket_reports/dynamic.xml?title=A+Dynamic+Report&conditions_string=version-eq-33441&fields_string=number,summary,hours_estimate_current,hours_actual’

Same deal. Condition is applied, fields are just the defaults, sans actual hours and percentage.

 
Avatar Steven Merrill 5 post(s)

For anyone reading this, word is that this is a legit bug and a fix is on the way.

 
Avatar David C. Administrator 283 post(s)

Steven,

We have gone ahead and added the hours-actual and percentage-complete fields to the report XML if they are specified in the fields-string. These will now work with both types of ticket reports.