Safety considerations and limited access to some of the data necessitated the introduction of additional features to the search engine.
In Secure Fields 3.0 we created 3 Search Security Levels, so you could choose which option is the best for your organization. You can set it up in the Search Security Level Configuration , in the Add-ons tab.
You can choose from 3 levels:
- Performance - gives you an option to easily search through Secure Fields with full JQL capabilities. The possible downside is that anyone will be able to perform search and see for instance values bigger/smaller than given amount, but still will not be able to see the preceise value of the Secure Field. This level enables fast and efficient search.
- Strict - has the same rules as the previous Secure Fields version had - limited JQL search, but harder for unauthorized people to find any information. Once you decide to upgrade to Secure Fields 3.0 all your secure fields will be automatically saved as Strict. We have also optimized search for this level, so if you decide to keep it this way, you will still feel the improvement in speed.
- Disabled - there is no option to search through Secure Fields.
+ you can also deifne your own "Custom" search level.
If you decide not to upgrade or stay with the Strict level of Security Search, you can still improve your efficiency search.
The Secure Field plugin adds "issue in search" function to the JQL. This function takes from 2 to 4 arguments rounded by quotation marks.
| Warning | ||
|---|---|---|
| ||
Please note that using the |
| Code Block |
|---|
issue in secureFieldSearch("", "", "") |
...
Operators that are defined for the particular field types are listed below:
| Secure Text | Secure Free Text | Secure Number | Secure List | Secure Multi Select List | Secure Single User Picker | Secure Multi User Picker | Secure Single Group Picker | Secure Multi Group Picker | Secure Date | Secure Date Time | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| = | x | x | x | x | x | x | x | x | x | x | x | ||||||||
| != | x | x | x | x | x | x | x | x | x | x | x | ||||||||
| > | x | x | x | ||||||||||||||||
| >= | x | x | x | ||||||||||||||||
| < | x | x | x | ||||||||||||||||
| <= | x | x | x | ||||||||||||||||
| isEmpty | x | x | x | x | x | x | x | x | x | x | x | ||||||||
| isNotEmpty | x | x | x | x | x | x | x | x | x | x | x | ||||||||
| startsWith | x | x | x | x | x | x | x | x | |||||||||||
| endsWith | x | x | x | x | x | x | x | x | |||||||||||
| contains | x | x | x | x | x | x | x | x |
In large instances ,due to better performance, please refer to functions described below as they allow to search within secure fields in a limited range of issues.
...
5 - case sensitive/insensitiv