This page documents known functional limitations of SearchMate.
These behaviors are intentional design decisions, not bugs, and are usually related to Jira’s internal execution or caching mechanisms.
Limitation 1: Jira built-in user-dependent and time-dependent JQL functions are not supported
Description
SearchMate does not support Jira’s built-in JQL functions that are time-dependent or user-context-dependent.
Why this limitation exists
SearchMate functions are evaluated and cached by Jira to improve performance and ensure consistent results.
User-dependent and time-dependent functions cannot be safely cached and may return incorrect or misleading results across users or executions.
To prevent this, SearchMate blocks such functions explicitly.
Affected functions
User-context dependent:
-
currentUser -
currentLogin -
lastLogin -
projectsWhereUserHasPermission -
projectsWhereUserHasRole -
componentsLeadByUser -
projectsLeadByUser -
myApproved -
myPending -
votedIssues -
watchedIssues -
issueHistory
Time-dependent:
-
now -
startOfDay -
endOfDay -
startOfWeek -
endOfWeek -
startOfMonth -
endOfMonth -
startOfYear -
endOfYear -
elapsed -
remaining
Recommended alternatives
-
Use static conditions instead of dynamic user or time functions
-
Replace user-based functions with explicit users, groups, or non-empty checks
-
Use fixed date ranges where applicable
Third-party JQL functions (from other apps) that depend on user or time may not trigger an error, but can still lead to incorrect results due to Jira caching.
Limitation 2: Cross-function nesting is not supported
Description
SearchMate only supports nested usage of the same function.
Mixing different SearchMate functions inside each other is not allowed, and will produce an error during execution.
To ensure reliable and consistent query evaluation, SearchMate restricts nested usage to the same function type only.
Unsupported example:
issueKey in linkedItemsFromQuery(
"project = TS AND issueKey in linkedItemsFromFilter(\"issueKey = FB\")"
)