Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to show all the options of a custom field when clicked the "Columns" button when searching

Michael Angelo Timoteo September 9, 2018

Hi all,

I am trying to make a JQL search and on the result set I click the "Columns" button to modify the column fields on my JQL search however I want to use a specific pattern called "Reason" and on our jira "Reason" is widely use like "Payslip Reason", "Reject Reason", "Pending Reason" and 30 more items and when I search the field "Reason" it is not getting query and select.

My goal is to select only the custom field called "Reason" but somehow it is not showing in the filtered result.

Refer to my screenshot.custom_field.pg.PNG

1 answer

0 votes
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2018

Hello,

Rename your Result field to a more meaningful name. It is strange to me to have more than 30 fields with the Result word in it and then just a Result field.

Michael Angelo Timoteo September 10, 2018

@Alexey Matveev,

Is there another workaround for this? This was doable before 7.9.2

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2018

Unfortunately, I do not know about another workaround.

Milan Chheda [INFOSYSTA]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2018

As Alexey mentioned, renaming is the best option in this case. Also, from the screenshot, it looks like lot of custom fields are created whereas those could have been clubbed  into 1-custom field having various options. 

Secondly, custom field naming should be as generic as possible as mentioned on below link:

https://confluence.atlassian.com/adminjiraserver/configuring-a-custom-field-938847235.html

"Make names as generic as possible — Give custom fields non-specific names that can be reused in other places later on. For example, instead of naming a field "Marketing Objective", name the field "Objective", and provide a description in the field configuration that states the Jira projects where that field is used."

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events