Adding quick filter on custom field

Amrita Nair

Hi,

I have created a custom field 'Platform' in my Kanban project which has multiple values in the list field (ex: unix, windows, etc). I am trying to apply it as a quick filter where users can select one of these and filter their cards. However, while writing the JQL, I see multiple 'Platform' fields popping up with different 'cf' values. I am not sure which one belongs to my project( I believe different projects might have the same custom field name and all of these get populated in the JQL drop down options. Please advise on mapping the correct platform field specific to my project. How to identify which one belongs to my project out of the list highlighted in red.

 

Walter Buggenhout

Hi @Amrita Nair,

There's a couple of things about your request here. To answer your question first: if you are logged in with jira administrator permission, navigate to the Custom Fields administration section (Admin / issues / custom fields) and locate your Platform custom field. Click the cog icon at the right hand site and hover over one of the options in the actions list (without actually clicking it). At the bottom of your screen, a url will show up showing the ID of the field, which is what you're looking for:

A simpler approach, possible without admin permissions, would be to go to the issue navigator (issues / search) and try searching the different Platform fields. The custom field ID will show up automatically behind the name of the custom field when in JQL view.

A few additional remarks though:

1. The use case you describe is one you will not be able to realise. Even if you get the right custom field, your users will not be able to select the options from a dropdown. Quick filters are static, meant to be toggled with a simple click. So you will need to set up a separate quick filter for each platform to get what you're after.
2. From a best practices perspective, having 6 custom fields called platform in your Jira instance is something you want to avoid. Instead, by using a single field with different field contexts would avoid what you are currently running into. Have a look at custom field documentation and consider fixing this or point your Jira administrator to the matter!