The following errors occur in the log file.

2011-10-21 17:05:37,858 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.jira.ext.charting:firstresponsedate'. Is the plugin present and enabled?
2011-10-21 17:05:37,898 main ERROR [jira.issue.managers.DefaultCustomFieldManager] Could not load custom field type plugin with key 'com.atlassian.jira.ext.charting:timeinstatus'. Is the plugin present and enabled?

Here's the answer from Atlassian. For more details and a discussion around this issue, see JSP-94659.

Hi Peter,

The error is actually due to the process JIRA uses to load functions/plugins and is harmless. Basically JIRA first loads the system required bundled-plugins, then it is followed by user-installed plugins. The error occurs between this process, before the user-installed plugins are loaded.

The Charting plugin adds multiple functionalities to JIRA, this includes adding 2 custom field types: 'First Response Time' and 'Time in Status'. This means that it is necessary for the plugin classes to be loaded for these customfield types to work. So basically when you restart JIRA, it will load the system bundled plugins and detect the customfields. This is where JIRA sees these customfields, but cannot match it with an associated class. After this, the user-plugins loads, aka the Charting Plugin and its classes, and everything works fine.

So in short, the error is thrown due to the startup procedures taken by JIRA. This is a harmless error.

Regards,

David Chan
Atlassian Support

Even though the suggestion is to ignore it, it is still an error and proper care should be taken of this. Unfortunately, as long as errors are logged, they should be addressed – and not ignored.