Can the more fields dropdown on filter be overridden?

We have a custom field that has several different (yet similar) contexts. When a user is searching issues across all projects and clicks on the More dropdown our custom field is unavailable. If the user limits their search to projects that have the same context of the custom field, then the field becomes available.

Is there a way to override this behavior? We'd like to have the custom field be available at all times and then handle any contextual differences within the code. 

1 answer

1 accepted

I finally figured this out so I'm documenting it here in case anyone else needs it.

In the Searcher defined for your custom field you'll need to override the SearchRenderer returned by getSearchRenderer(). In your custom SearchRenderer you'll need to override what is returned by the isShown method. 

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

708 views 6 13
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you