Wrong Custom Field Displayed on an Issue Screen

Symptoms

When seeing a Screen in JIRA, a different Field is displayed rather than the one configured. You can see in the example below that the Story Points field is being displayed three times in the screen:

However, looking on the Screen configured for this Project/Issue Type, the original fields are correctly configured, and the Story Points is only appearing once:

Cause

The Field Configuration of the custom field is mistakenly pointing to the Field Configuration of another Custom Field instead of it's own. This is similar to the problem described on this other knowledge base article, but what causes both of these problems is still unknown.

Resolution

1. First of all, get the id of the Custom Field being mistakenly displayed:

   1 select * from customfield where cfname = '<CustomFieldName>';

   For example, '10002' will be returned. So replace '10002' in the following queries with the id you got from the query above.

2. Then, verify what are the incorrect entries. To do so, please run the following:

   1 select * from fieldconfigschemeissuetype where fieldconfiguration in (SELECT id FROM fieldconfiguration WHERE fieldid = 'customfield_10002') AND fieldconfigscheme not in (select id from fieldconfigscheme WHERE fieldid = 'customfield_10002');

   Here it should be returned one row for each association between the corrupt custom field and an issue type. For example, if the field is associated with two Issue Types, two rows should be returned. (Please note it is possible more than one custom field is being affected).

3. Using the value of the 'fieldconfigscheme' returned, run the following:

   1 select * from fieldconfigscheme where id = 14902;

   If more than one custom field is being affected, you'll see different values in the 'fieldconfigscheme' column, and in this case choose one of them. Keep the value of the 'fieldid' returned, which will be used in the queries below. (e.g. 'customfield_14302').

4. Now, run the below to get the correct 'fieldconfiguration' of the custom field to correct the association:

   1 select * from fieldconfiguration where fieldid = 'customfield_14302';

   Replace 'customfield_14302' with the value returned in the previous step. Also, keep the value of the 'id' returned for future use (e.g.: 15502).

5. With the data gathered with the previous queries, run the following query to correct the associated values and consequently fix this issue:

   1 update fieldconfigschemeissuetype set fieldconfiguration = 15502 where fieldconfigscheme = 14902;

   You'll just need to replace the fieldconfiguration value with the one returned on step #4 and fieldconfigscheme with the one used in step #3.