So if you are creating a saved filter that you expect to be used by anonymous users, do not use this function. Returns issues that have an SLA that has completed at least one cycle. It is possible for an issue to belong to both a completed Sprint(s) and an incomplete Sprint(s). Search for requests that required approval and have a final decision of approved. You can use a JQL filter to make a board that shows the relevant issues based on whatever criteria you want. JQL is a flexible yet robust logic that can be used in a variety of different ways.

Search for issues that were updated by a specific user, optionally within the specified time range. The “WAS IN” operator is used to find issues that currently have or previously had any of multiple specified values for the specified field. Or use “w” (weeks), or “d” (days) to specify a date relative to the current time. Unlike some other functions, updatedBy doesn’t support values smaller than a day, and will always round them up to 1 day.

Download the JQL Cheat Sheet

Perform searches based on the earliest unreleased version in a project. See also startOfWeek, startOfMonth, and startOfYear; and endOfDay, endOfWeek, endOfMonth, and endOfYear. Search for requests that currently or previously required approval by the current user. Search for requests that require approval or have required approval by the current user. You can restrict the search to links of a particular type.

You can also search on the released versions of all projects, by omitting the project parameter. Find issues in projects where you have a specific permission. Find issues in projects that are led by a specific user.

Dailymotion Keyboard Shortcuts

Perform searches based on the unreleased versions (i.e. versions that your Jira administrator has not yet released) of a specified project. You can also search on the unreleased versions https://deveducation.com/ of all projects, by omitting the project parameter. Perform searches based on the released versions (i.e. versions that your Jira administrator has released) of a specified project.

Note that this function can only be used by logged-in users. Perform searches based on issues jql contains for which you have voted. Note, this function can only be used by logged-in users.

issueHistory()

By default, this function considers Sunday to be the first day of the week. You can use a different day (for example, Monday) as the start of the week. If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. startOfDay(“+1”) is the same as startOfDay(“+1d”). The keyword “none” can be used to search for issues where either or both of the options have no value.

• The “WAS NOT IN” operator is used to search for issues where the value of the specified field has never been one of multiple specified values.
• Search for new issues created since the start of the first day of the current week.
• Search for requests that currently or previously required approval by the current user.
• As a result, the above query will return all issues that do not have an assignee that are at least one day old.
• You can also search on the released versions of all projects, by omitting the project parameter.

If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. endOfWeek(“+1”) is the same as endOfWeek(“+1w”). If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. endOfMonth(“+1”) is the same as endOfMonth(“+1M”). If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. endOfDay(“+1”) is the same as endOfDay(“+1d”). Find issues in components that are led by a specific user.