Forums

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

Bulk change does not show all fields for one user

Justin Munos
August 22, 2022

jiraIssue.png

Bulk change on Jira only shows two date fields for me. I cannot see all fields while bulk changing issues, just these two date fields. This error occurs on every project that I create and am apart of, even projects that don't include these two date fields.

 

I have tried using bulk change on other computers/devices as well as different internet browsers and this issue still occurs. This issue seems to be tied to my account only, any other users within my workplace can see all fields when using bulk change. I have the same account permissions as them as well.

 

Is there any fix for this issue?

2 answers

0 votes
Nic Brough -Adaptavist-
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 Champions.
September 9, 2012

I don't think there's a way to do this - the whole point of JQL is that it's powerful and can search anything. The project clause could be used anywhere in the search, and doesn't even have to be used at all.

I suspect you'd need to pull the whole of JQL apart and rewrite it to make this work.

I'd train your users to use the simple search instead, and think about how you limit your custom field contexts. Simple search DOES do the "is field valid for this project/issue type" limiting automatically, so I think your only option is to use that.

0 votes
Krzysztof Skoropada [Deviniti]
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 Champions.
September 9, 2012

Hi,

What you can do is set Search Template to None in customfield's configuration page - will not be searchable but this will affect for any project.

Moshe Hajaj
Contributor
September 9, 2012

The thing is that 80% of my projects are prety slim, but those 20% have a huge number of custom fields. Putting "none" in their configuration will make these projects un-searchable. I don't want to cancel the ability of these projects' users to search their projects, create filters & gadgets. and so on.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events