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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs