-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Issue Summary
Currently, Jira users are unable to search the issues via the UpdatedBy function if Safeguards is enabled (this is the default behavior since Jira 8.22.2 and also backported to 8.20.12). The feature allows only these fields to be searched:
- Assignee
- Fix Version
- Priority
- Reporter
- Resolution
- Status
Steps to Reproduce
- Install Jira 8.22.2 or newer
- Update one of the fields except the ones above
- Search for this update via the updatedBy function
Expected Results
Admins should have a feature to select the fields so that they can be searched via UpdatedBy function
Actual Results
The issue will not appear in the search results.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available. However, you can set jira.safeguards.indexing.issue.changelogs.do.not.filter.out.unsupported.fields parameter to true to disable the Safeguards. However, this is not recommended because if unsupported fields aren’t filtered out, this may cause performance degradation for large issues. You can identify issues with large change items and change groups by running a database query. For details, see Retrieve issue change history from database in Jira server.
- is related to
-
JRASERVER-73874 Reindexing issues with large number of comments, worklogs, history overloads indexers
- Closed
-
JRASERVER-76321 Create additional safeguards for locked custom/system fields
- Gathering Interest