How to remove any entries related to Minyaa from the logs
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Even after remove the Minyaa plugin from JIRA, some WARNs are still appearing in the log files.
The following appears in the atlassian-jira.log:
1
2014-12-01 11:00:00,098 atlassian-scheduler-quartz1.clustered_Worker-1 WARN[jira.plugin.customfield.CustomFieldSearcherModuleDescriptorsImpl] Custom field searcher module: jira.plugin.minyaa.tools:textsearcher is invalid. Null being returned.Cause
Minyaa Tools provides the RegExpField customfieldtype. Each customfieldtype requires a customfieldsearcher.
To reuse this default searcher, Minyaa declares the TextSearcher class as compatible with RegExpField and also existing default Text customfield.
Apparently, the impact is that any created Text Field created with Minyaa installed, has been created using the Searcher defined in Minyaa.
Resolution
Run the following query to see if there are any searchers defined in Minyaa:
1
SELECT * FROM users;If so, backup your JIRA and run the following query to update those entries:
1
2
UPDATE customfield c SET customfieldsearcherkey = 'com.atlassian.jira.plugin.system.customfieldtypes:textsearcher'
WHERE customfieldsearcherkey ='jira.plugin.minyaa.tools:textsearcher';Was this helpful?