Filters for Releases, Sprints (Iterations) and Team Iterations | Targetprocess - Visual management software

Filters for Releases, Sprints (Iterations) and Team Iterations

These Advanced Filters help to select, hide or highlight data in planning and tracking Views and Visual Reports. You can filter your cards by Releases, Sprints (Iterations) and Team Iterations they belong to. Also you can filter cards and lanes that represent Releases, Sprints (Iterations) and Team Iterations themselves.

Assignable entities are work items such as User Stories, Bugs, Tasks, Features, Epics, Requests, Test Plan Runs, Test Plans. Filters below are work for any of these types of entities selected as cards.

EntityFilterResult
Assignable?Release is '2.0'

?Iteration is '2.0.1'

?TeamIteration is 'Beta'

Entities from the Release '2.0' / Iteration '2.0.1' / TeamIteration 'Beta'.
Assignable?Release is None

 

Entities not assigned to any Release. Filters for Sprint (Iteration) or Team Iteration work the same way.
Assignable?Release is not None

 

Entities assigned to any Release. Filters for Sprint (Iteration) or Team Iteration work the same way.
Assignable?Release is not '2.0'Entities from any Release, but '2.0'. Entities not assigned to any Release are excluded. Filters for Sprint (Iteration) or Team Iteration work the same way.
Assignable?Release is '2.0' or Release is NoneEntities from any Release, but '2.0'. Entities not assigned to any Release are included. Filters for Sprint (Iteration) or Team Iteration work the same way.

Keywords supported in filters

Current, Future and Past keywords help to filter Releases, Sprints (Iterations) and Team Iterations that are in progress, next or past.

Current

Current Releases, Sprints (Iterations) and Team Iterations have Start Date set to today or a past date and End Date set to today or a date in future.

EntityFilterResult
Release

Sprint (Iteration)

Team Iteration

?It is Currentonly current scopes of work
Assignable?Release is Current

?Iteration is Current

?TeamIteration is Current

all the entities from the current scopes of work

Future

Future Releases, Sprints (Iterations) and Team Iterations have both Start Date and End Date set to dates in future.

EntityFilterResult
Release

Sprint (Iteration)

Team Iteration

?It is Futureall future scopes of work
Release

Sprint (Iteration)

Team Iteration

?It is Future(2)takes COUNT of next Releases, Sprints (Iterations) or Team Iterations

works as filter, not supported in Visual Encoding rules

Assignable?Release is Future

?Iteration is Future

?TeamIteration is Future

all the entities from the future scopes of work
Assignable?Release is Future(2)

?Iteration is Future(2)

?TeamIteration is Future(2)

all the entities from the COUNT of next Releases, Sprints (Iterations) or Team Iterations

works as filter, not supported in Visual Encoding rules

Past

Past Releases, Sprints (Iterations) and Team Iterations have both Start Date and End Date set to past dates.

EntityFilterResult
Release

Sprint (Iteration)

Team Iteration

?It is Pastall past scopes of work
Release

Sprint (Iteration)

Team Iteration

?It is Past(2)takes COUNT of last Releases, Sprints (Iterations) or Team Iterations

works as filter, not supported in Visual Encoding rules

Assignable?Release is Past

?Iteration is Past

?TeamIteration is Past

all the entities from the past scopes of work
Assignable?Release is Past(2)

?Iteration is Past(2)

?TeamIteration is Past(2)

all the entities from the COUNT of last Releases, Sprints (Iterations) or Team Iterations

works as filter, not supported in Visual Encoding rules

More examples

EntityFilterResult
Release

Sprint (Iteration)

Team Iteration

?It is Current or It is Futurecurrent Release, Sprint (Iteration) or Team Iteration and all next ones
Feature?UserStories.Where(Iteration is Current)features with user stories from the current iteration

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.