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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,335 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot