How to limit fields in Jira search

[Jeanne Howe]

I believe that, when working in JIra on-prem, if you set a field configuration scheme for a project any JQL searches created with the project would be limited to the fields within the project field configuration. In other words, they would not see EVERY field in Jira. 

In Jira cloud, I am not able to make this happen. I have several projects that have a specific set of fields. When they create a JQL search, they only want to see the fields used by their projects, not every field ever created in Jira. 

Can this be done in JIra Cloud?

[Petter Gonçalves]

Hello Jeanne,

Thank you for reaching out.

Actually, JQL queries for both Jira Cloud and Jira Server (8.7) do not consider specific field configuration schemes when setting the project in the query, so it allows you to set any fields in the query, although I'm not sure if a past version of Jira Server allowed this setting.

Anyway, can you please provide us with more details on why do you need that kind of restriction in your JQL query? What are you are trying to achieve exactly?

Fields can be added or removed from your issue navigator, optionally selecting which ones you want to display as columns, so I'm not sure how that kind of restriction can benefit any functionality in Jira Cloud.

Please, let us know how you can help you. :)

[Jeanne Howe]

Petter,

We have to use cases - 

1 - We have several different types of users in Jira - Business, Technology, Laboratory. When creating JQL searches, our business and lab teams do not want to see fields used in Technology (since they do not use those fields). The business and lab teams have much fewer custom fields than the technology teams, so having all of the fields showing is very confusing for them.

2 - We have fields used in specific projects only. Sometimes this is due to security reasons and sometimes due to process reasons. We do not want these fields listed in the JQL search. I understand that unless a user has access to the projects these fields are used in, they can not see the data however, the fact that users can see these fields listed within the JQL raises a lot of questions about what these fields are and how they are used.

[Jeanne Howe]

@Petter Gonçalves Any feed back on my use cases?

[Petter Gonçalves]

Hello @Jeanne Howe

Sorry for my late reply and thank you for your reminder.

We understand the value of your suggestion to only display the fields related to the project's field configuration when finishing your JQL query. Indeed, it is not currently applied in Jira Cloud.

That being said, we created the following feature request so our developers can take it under consideration:

- Only Display fields added in the field configuration when selecting projects in JQL queries 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Let us know if you have any questions.