Info |
---|
Security levels remind:
Important: changing Security level always demands Jira re-index, otherwise changes will not be saved. |
Common problems:
Expand | ||
---|---|---|
| ||
The error occurs when JQL is used to search for the field that is set to Strict mode. There are 2 ways of resolving the issue:
|
Expand | ||
---|---|---|
| ||
Secure Fields app provides an option to migrate existing custom fields to secure ones. In case of Default search security level is set to Performance, you might not be able to search for the migrated field and warning will be showed on a Search |
...
settings page. It appears because the security level was changed |
...
and now it’s incompatible with the current configuration. To fix it, simply click on Performance button once again, press Save changes and re-index your Jira. |
After performing a migration If field was automatically set to Performance mode
Secure Single/Multi List in Performance mode -> not supper secure suggest strict mode, reindex jira or at leaset project
Switching from Strict to Performance, reindex Jira or at least project, check global search setting, then setting for particular CF
...
search that you perform
...
secure field's permission scheme
...
searching mode settings: Manage apps → Secure Fields → Search Security Settings
...
secure field settings: Issues → Custom fields → pick needed secure field and press Edit
...
Troubleshooting checklist:
1. make sure the search is performed by the user who is authorized to view the secure field
2. make sure there are no typos in the search query
3. use searching query according to Secure level searching mode settings:
for JQL search - Search level has to be set to Performance
JQL search won’t work for fields in Strict mode, you will have to use "issue in search" function or switch to Performance mode
4. check if there is no warning for the particular field on Search security level page, if warning sign occurs - save configuration once again and perform re-index.