Within Nestr you can always quickly find your nests by searching for the name, purpose, contents or discussion of the nest.

It's important to note that the Nestr search is context sensitive, which means it will only search for your items starting at your current level. You can always find out your current level and navigate higher up by using the breadcrumbs. The counts next to each breadcrumb show the total amount of results for each level.


You can also use the search syntax to filter your results on specific attributes like labels or assignee.

label:project assignee:me

When typing these command an autocomplete will show up to help you complete your commands and their values.


To easily filter out specific nests you can use negation by using the exclamation character! . For example:

label:!project assignee:!me


assignee filters on the assigned users, values can be me or the email address of a user. For example to show all nests assigned to me or Joost:

assignee:me assignee:joost@nestr.io


label filters on the label of the nest. You can use negation and multiple values to create advanced searches, for example to show all projects and bugs that don't have the someday and later labels:

label:project,bug label:!$someday,$later

Note: labels prefixed with a $  sign are personal or workspace labels, labels without a prefix are global labels. We expect this requirement to be removed in a future version of Nestr. When using the autocomplete the system will automatically prefix the appropriate labels.


completed allows you to search for tasks that have or haven't been completed
Note: to see completed items you might need to disable the default filter of Hide completed Nests.



Type allows you to filter between a nest and a comment.



Using has allows you to filter on all kinds of attributes like if the item is completable or has any children.


To get all your projects which still have unfinished subtasks you could use the incompletechildren property.

label:project has:incompletechildren


Using depth and mindepth you can limit to how many levels deep you want to search. The current level is 1, so if you want to limit your search results to your current level/context you can use


Mindepth allows you to define the minimum depth you want to see, for example if you only want to see subtasks which are part of projects of your current context you could use


Parent label

Parent label allows you to find items which fit under a certain type of parent. For example in Holacracy you could use it to find all the projects and tasks for a certain role


Or you could use it to find all subtasks from projects which are assigned to you

assignee:me parent-label:project


The results you find are default shown in their search order (which tries and default to the order the item had in it's parent). Within this search you can re-order items and they will keep this order within similar searches.

Because of the structure of your data, this default order can be unexpected and confusing so within the search it's also possible to have the results in a self defined order.

sort:title sort-order:asc

The sort-order defaults to ascending when left out, but can also be set to a reverse sort, for example to show the latest changes.

sort:updatedAt sort-order:desc

Did this answer your question?