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.
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.
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 ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot