Secure Fields for JIRA
Page tree

Versions Compared

Old Version 11

changes.mady.by.user Inga

Saved on

compared with

New Version Current

changes.mady.by.user Inga

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Security levels remind:

  1. Performance - you can perform regular JQL search. 

  2. Strict - you can search for secure fields only by using "issue in search" functions.

  3. Disabled - search is not possible.

Important: changing Security level always demands Jira re-index, otherwise changes will not be saved.

Common problems:

Expand
titleThe field is not searchable, it is only sortable / no results / outdated results

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:

  1. switching to Performance mode to enable field search via JQL;

  2. keep Strict mode and use one of "issue in search" functions.

Expand
titleThe field is not searchable after migration

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.

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.