Unable to add Security Level field in Basic filter
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
Adding Security Level field in Basic issue filter.
原因
There is a Switching between 'Advanced' and 'Simple' Search documentation related to this issue where it stated:
- In general, a query created using 'Simple Search' will be able to be translated to 'Advanced Search' (i.e. JQL), and back again.
- However, a query created using 'Advanced Search' may not be able to be translated to 'Simple Search', where
In this case Security Level Field in the Issue can only queried using Advanced Search.
回避策
Security Level is not accessible from basic search in the current implementation.. A query created using 'Advanced Search' may not be able to be translated to 'Simple Search', particularly if:
the query specifies a field and value that is related to a project (e.g. version, component, custom fields) and the project is not explicitly included in the query (e.g. fixVersion = "4.0", without the AND project=JRA). This is especially tricky with custom fields since they can be configured on a Project/Issue Type basis. The general rule of thumb is that if the query cannot be created in the 'Simple Search' form and if it is created using 'Advanced Search' , then it will not be able to be translated to 'Simple Search'.
In this case Security Level Field in the Issue can only queried using Advanced Search following this KB :