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

Accepted Answer
0 votes

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
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

22,362 views 2 7
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