Custom Field has different option value IDs

[seanryanirl]

Hi, we are moving from Jira 3.13.2 to Jira 5.2.

We notice that once the backup is complete with the new instance we are having issues with some of our custom fields. The problem is that the option values are different from our old jira instance which is causing us problems.

For example

The select list in the old system for a particular custom field has the following:

<option value="1">1</option>

But in the new instance the same custom field has the follow:

<option value="11031">1</option>

This is causing us issues as we use javascript to populate certain fields.

Can you help us out here please,

Thanks,

Sean

[James Winters]

Yeah, in build 633 we changed from storing the option values to storing the option id - this is actually a much more sensible approach as there's less chance of conflict. I'm afraid is does mean you're going to have to redo your javascript to use the custom field option id rather than the option value.

[Nic Brough [Adaptavist]]

You'll need to amend your javascript.

Somewhere around version 4.3 (Sorry, I can't remember the exact release), the schemes were changed quite drastically. Before the change, an "option" was a simple string which was stored in the list of options, and then on the issue custom field when you used it. It's been changed to an ID-and-label format - Jira works with the IDs internally, but displays the label. This allows you to rename options, and is more consistent with the rest of Jira.

I can't tell you what javascript you'll need to amend, but you'll need to deal with this new structure. In your example above, you can safely rely on the "value=11031" being immutable, but the display of that can now change.