SOAP script broken after JIRA 5 upgrade

[Paul Stahlke]

When we upgraded from JIRA 4.4.4 to 5.0.7, our script broke. The lookup for a cascading select custom field value is returning the ID now instead of the Value. Does anyone know how to fix this?

I think the problem is here:

my @cfs=("customfield_10459","customfield_10458","customfield_10741","customfield_10031","customfield_10060","customfield_10451");

my $values = $jira->get_issue_custom_field_values($issue,@cfs);

We tried to extract the values for 'customfield_10451' which is a cascading select field, it used to be a string value(e.g. “New York”), now became an internal ID (e.g. 11771).

'customfieldId' => 'customfield_10451',

'values' => [

'11771'

],

'key' => undef

[Paul Stahlke · Accepted solution]

We decided to use the REST API for resolve this.

[Tom Towkach]

You may be hitting an improve to JIRA. JIRA is now storing the option ids instead of option name. This was changed to introduce option renaming.

Have a look at the customfieldoption table to find the String value for that option using the id you got from customfieldvalue table.

I thought this change was released in 4.4.4 already, but check that table to see if you see your values. If they are now then you'll have to get the value for that option from that table.

[Paul Stahlke]

Yes, that is the case. So how do I pull in the value instead on a soap call?

[Tom Towkach]

That's a good question. Starting in JIRA 5.0, the REST API became the recommened and supported remote API for JIRA. REST is where Atlassian is adding functionality to the remote API (https://developer.atlassian.com/display/JIRADEV/Creating+a+JIRA+SOAP+Client) . Your SOAP script will continued to be supported, but probably if you want an api call to to get that value for you, I'm guessing, it wont be there in the SOAP remote API. It might in the REST API. You could switch to REST and use that or stick with your SOAP script. If there is no api call for you to use, then your script will have to query the database and do the join to the customfieldoption table as I mentioned above.