Filters by field. Filtering functions.

To create a field-based filter, click on “+“ icon on the Filter panel.

Field	Choose either Gantt or Jira field from the drop-down menu
Operator	Select an operator (“=“, “!=“, “empty“, “not empty“, “in“, etc.)
Value/Function	Type a value or choose a function is applicable
Name	Provide a filter name

For instance, you would like to see only the unassigned tasks in Gantt chart. In such case, you can create a filter based on Gantt field Resource. Note that you can use either operator “=“ or “empty“.

Resource = Unassigned or Resource is empty

Please see below.

Functions supported by Gantt Suite

Please note: If impersonation is enabled for a chart (configured under the Security tab), JQL filters that use functions will execute in the context of the impersonated user.
For example, the JQL filter assignee = currentUser() will return issues assigned to the impersonated user, which may differ from the currently logged-in user.

	Function	Supported fields	Supported operators	Unsupported operators	Examples	Notes

Function	Supported fields	Supported operators	Unsupported operators	Examples	Notes
closedSprints()	Sprint	`IN , NOT IN`	`= , != , ~ , !~ , > , >= , < , <=` `IS , IS NOT, WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED`	Find all issues that are assigned to a completed sprint: `sprint in closedSprints()`
currentUser()	Assignee, Reporter, Resource (Gantt)	`= , !=`	`~ , !~ , > , >= , < , <= IS , IS NOT , IN , NOT IN , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED`	Find issues that are assigned to me: `assignee = currentUser()`
endOfDay()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find issues due by the end of today: `due < endOfDay()` Find issues due by the end of tomorrow: `due < endOfDay("+1")`	`endOfDay() endOfDay("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` 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"). If the plus/minus (+/-) sign is omitted, plus is assumed.
endOfMonth()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find issues due by the end of this month: `due < endOfMonth()` Find issues due by the end of next month: `due < endOfMonth("+1")`	`endOfMonth() endOfMonth("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` 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 plus/minus (+/-) sign is omitted, plus is assumed.
endOfWeek()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find issues due by the last day of the end of this week (by default, the last day is Saturday): `due < endOfWeek()` Find issues due by the end of this week (last day as Sunday): `due < endOfWeek("+1d")`	`endOfWeek() endOfWeek("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` 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 plus/minus (+/-) sign is omitted, plus is assumed.
endOfYear()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find issues due by the end of this year: `due < endOfYear()`	`endOfYear() endOfYear("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. endOfYear("+1") is the same as endOfYear("+1y"). If the plus/minus (+/-) sign is omitted, plus is assumed.
futureSprints()	Sprint	`IN , NOT IN`	`= , != , ~ , !~ , > , >= , < , <=` `IS , IS NOT, WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED`	Find all issues that are assigned to a sprint that hasn't been started yet: `sprint in futureSprints()`
linkedissue	Issue	=, !=		Find subtasks that are linked to a particular epic: `linkedissue = epicKey-123`
linkedIssues()	Issue	`IN , NOT IN`	`= , != , ~ , !~ , > , >= , < , <= IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED`	Find issues that are linked to a particular issue: `issue in linkedIssues(ABC-123)` Find issues that are linked to a particular issue via a particular type of link: `issue in linkedIssues(ABC-123,"is duplicated by")` Find issues that are linked to a particular issue via any type of link specified: `issue in linkedIssues(ABC-123,"is duplicated by", "is blocked by")`	`linkedIssues(issueKey) linkedIssues(issueKey,CaseSensitiveLinkType) linkedIssues(issueKey,CaseSensitiveLinkType, CaseSensitiveLinkType)`
now()	Created. Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find issues that are overdue: `duedate < now()`
openSprints()	Sprint	`IN , NOT IN`	`= , != , ~ , !~ , > , >= , < , <=` `IS , IS NOT, WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGED`	Find all issues that are assigned to a sprint that has not yet been completed: `sprint in openSprints()`
startOfDay()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find new issues created since the start of today: `created > startOfDay()` Find new issues created since the start of yesterday: `created > startOfDay("-1")`	`startOfDay() startOfDay("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` 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"). If the plus/minus (+/-) sign is omitted, plus is assumed.
startOfMonth()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find new issues created since the start of this month: `created > startOfMonth()` Find new issues created since the start of last month: `created > startOfMonth("-1")`	`startOfMonth() startOfMonth("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. startOfMonth("+1") is the same as startOfMonth("+1M"). If the plus/minus (+/-) sign is omitted, plus is assumed.
startOfWeek()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find new issues since the first day of the start of this week (by default, the first day is Sunday): `created > startOfWeek()` Find new issues since the start of last week: `created > startOfWeek("-1")`	`startOfWeek() startOfWeek("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. startOfWeek("+1") is the same as startOfWeek("+1w"). If the plus/minus (+/-) sign is omitted, plus is assumed.
startOfYear()	Created, Due, Resolved, Updated, custom fields of type Date/Time	`= , != , > , >= , < ,`	`~ , !~ IS , IS NOT , IN , NOT IN`	Find new issues since the start of this year: `created > startOfYear()` Find new issues since the start of last year: `created > startOfYear("-1")`	`startOfYear() startOfYear("inc")` _where`inc` is an optional increment of `(+/-)nn(y\|M\|w\|d\|h\|m).` If the time unit qualifier is omitted, it defaults to the natural period of the function, e.g. endOfYear("+1") is the same as endOfYear("+1y"). If the plus/minus (+/-) sign is omitted, plus is assumed.

Once a filter is created, it is enabled.

The enabled filter is highlighted in blue as shown below.

Note that the Filter button is highlighted in blue in case there is at least one enabled filter. This is helpful if the Filter panel is hidden and the fact that there are enabled filters is not obvious.

To enable or disable a filter, simply, click on it, or use the filter’s drop-down menu.

Note that the filter’s drop-down menu offers the ability to edit or delete the filter.

Filter templates

The “+“ icon on the Filter panel offers quick access to filter templates such as Issue type (filter by issue type), Resource (filter by resource) and Status (filter by status).

The filter templates have pre-selected fields and operators.

To continue with earlier example when the requirement is to see only unassigned tasks, you can use the template Resource as shown below.

To differentiate between Gantt and Jira fields when creating a field-based filter please visit page Gantt fields

If needed a user can filter tasks by Flags, using the field-based filter.

Task markers, Flags

For instance, you want to see only the tasks that have missed their deadlines.

Advanced filter

Starting from version 7.0, the Advanced Filter feature is available, allowing you to combine multiple conditions using AND/OR operators.

To create an advanced filter:

Click Advanced in the Filter panel.
Create the first condition, then click Next.
Add more conditions by selecting either the AND or OR operator.
Once all conditions are added, enter a name for the filter and click Save.

For example, suppose you want to view unassigned tasks with high priority or tasks that are due by the end of the month.

You can create this filter by following these steps:

Click Advanced in the Filter panel.
Create the first condition: Resource is empty, then click Next.

Add the second condition using the AND operator:
Priority in Blocker, Highest, High (note: available options may vary depending on your Jira configuration), then click Next.

Add the third condition using the OR operator:
due <= endOfMonth(), then click Next.

Enter a name for the filter and click Save.