invalid legacy custom fields

[Olivier Bourquin]

Hello,

We were using a go2group plugin that created custom fields of special type. We have deinstalled the plugin long ago, but upon subsequent upgrades of jira, their values stayed in the DB. Since the type is not valid anymore, the custom fields are not shown anymore, but in the log file we always have those types of errors:

{noformat}

jira.issue.managers.DefaultCustomFieldManager Could not load custom field type plugin with key 'com.go2group.jira.plugin.mercury_kit:mercury_field'. Is the plugin present and enabled

{noformat}

Now i'd like to get rid of this, but i'm not sure how. I've researched a little in the database, and found the fields:

{noformat}

mysql> select id, customfieldtypekey,cfname from customfield where cfname in ('JAP QC - Test Cases' ,'Overdue','Requirements') ;

+-------+----------------------------------------------------+---------------------+

| id | customfieldtypekey | cfname |

+-------+----------------------------------------------------+---------------------+

| 10290 | de.phil.jira.plugin.overduefield:overduefield | Overdue |

| 10315 | com.go2group.jira.plugin.mercury_kit:mercury_field | JAP QC - Test Cases |

| 10341 | com.go2group.jira.plugin.mercury_kit:req_field | Requirements |

+-------+----------------------------------------------------+---------------------+

{noformat}

Would it be ok if i would delete all entries in customfieldvalue, customfieldoption and customfield where the id is one of those three?

Or am I missing something?

That's what i would execute:

{noformat}

delete from customfieldvalue where customfield in ( 10290 , 10315, 10341)

delete from customfieldoption where customfield in ( 10290 , 10315, 10341)

delete from customfield where ID in ( 10290 , 10315, 10341)

{noformat}

Help would be appreciated.

Cheers

Olivier

[Dieter · Accepted solution]

Please check this link http://confluence.atlassian.com/display/JIRA043/Database+Schema#DatabaseSchema-Customfields It contains all tables referring to the customfield. You should not forget configurationcontext and fieldconfigscheme.

[Arthi Balraj]

Facing same issues while exporting projects .

Can anyone suggest as this plugin is not in use can we remove the customfield id's in DB?

Please confirm