To define what items you want to see in a view, you write a formula in the view’s Items field. The pattern you have for defining a view is that you have a start item and then you follow contexts and/or individual relation types to arrive at some items you want to see. In the chapter “Creating folders” the start items were defined by
ITEMSOFTYPE(“Product”:1234567), i.e. any item that is of type “Product”. However, when we want to define a view for a particular Product, we are usually want to define the start item with the function NODE().
NODE() refers to the so-called context item. In other words, we could have in the menu multiple products, Product 1, Product 2 etc, but when we open Product 1 (=context item), we want to see in the tree view items that are specifically related to it, and not to those other products.
We have four ways to follow the items from our start item. The double arrow operator (->>, also called “expand”) will include the start items and all the items that on the path of the relation types when “expanding” forward from the start item. For instance it the example in the Creating folders chapter we used ->> because we wanted to see both our Products and the Releases there was for each product.
Alternatively we could use a simple arrow (->, also called “hop”). The simple arrow makes a single hop from the start item. It could be used for instance to show in a list all the Features that a Product has in its backlog.
In addition to the above operators, we have <<- and <- which are otherwise the same as their sisters above, but follow the relation types and contexts in the other direction.
One last thing to know are the filter operators.