custom searcher for multiple custom field is not visible

Dmitriy_Shalygin November 13, 2019

jira core (server) 7.12

I wrote seacher for multiple custom field, but it is not visible when i edit field config. 

Logs say this searcher is created. 

<customfield-searcher name="Multi Text Searcher" i18n-name-key="multidepsearcher.name" key="multidepsearcher"
class="nemavasi.jira.edo.company.cf.MultipleValuesSearcher">
<description key="nmv-text-searcher.description">The Multi department Searcher Plugin</description>
<valid-customfield-type package="nemavasi.jira.edo.company.cf" key="nemavasi-jira-custom-multi-department-chooser-cf"/>
<resource name="search" type="velocity" location="/templates/cf/multichooser/text-searcher/search-basictext.vm"/>
<resource name="view" type="velocity" location="/templates/customfields/text-searcher/view-searcher-basictext.vm"/>
</customfield-searcher>

 

    <customfield-type name="Custom multi department chooser CF"
i18n-name-key="Department Multi Chooser"
key="nemavasi-jira-custom-multi-department-chooser-cf"
class="nemavasi.jira.edo.company.cf.MultiDepartmentChooserCF">
<description key="Custom multi department chooser">
Custom multi chooser for department
</description>
<resource name="view" type="velocity"
location="templates/cf/multichooser/department/view-readonly-chooser.vm"/>
<resource name="column-view" type="velocity"
location="templates/cf/multichooser/department/view-readonly-chooser.vm"/>
<resource name="xml" type="velocity"
location="templates/cf/multichooser/department/view-readonly-chooser.vm"/>
<resource name="edit" type="velocity"
location="templates/cf/multichooser/department/edit-chooser.vm"/>
<!-- <valid-searcher-->
<!-- package="com.atlassian.jira.plugin.system.customfieldtypes"-->
<!-- key="textsearcher"/>-->
<!-- -->
</customfield-type>

 

If i uncomment valid-searcher it (text seacher, not mine) is visible for selection when i edit field config.  

Why is my seacher invisible when i edit field config  ? 

 

1 answer

1 accepted

0 votes
Answer accepted
Dmitriy_Shalygin November 19, 2019

Sorry, my mistake was a wrong value in  "

valid-customfield-type package

"

Suggest an answer

Log in or Sign up to answer