Skip to main content

Format a list property: add views with their own filter, fields, and layout

Add named views to a list property, each with its own filter, fields, and table or list layout, and choose which view it opens on

Format a list property: add views with their own filter, fields, and layout

A property set to List of values holds many items in one work item: the line items on an invoice, the contacts on an account, the tags on a ticket. Viewers can always see the list two ways:

  • Table shows one row per item. A list of objects gets one column per field. A list of plain values, such as text or numbers, is a single column.

  • List shows each item on its own line, in full.

Both show every item and every field, and they are always there. A property's Format adds views of your own beside them. Each view has:

  • a filter: which items it keeps, for example only Open line items,

  • for a list of objects, its fields: which of the item's fields it shows, and

  • a layout: Table or List.

Format only changes how the list is shown. The stored items stay the same, and so does what the AI agent reads and writes. A number's currency setting and a date's display format work the same way.

Add a view

  1. Edit the property in the thunk's data structure.

  2. Choose List of values. The Format section appears at the end of the property's settings, below Required.

  3. Select Add view. In the dialog:

    • Give the view a short, unique View name. Viewers pick the view by this name. It can't be Table or List.

    • Under Show as, choose Table or List.

    • Under Items, build the condition for the items the view keeps. With no condition, it keeps every item.

    • For a list of objects, under Fields shown, switch off the fields the view should hide.

  4. Select Save. The Format section sums the view up in one line, for example Open: status = "open", showing Item and Owner, in Table mode.

  5. Under Opens on, choose the view the list shows first: one of yours, Table, or List. If you don't choose, it opens on Table.

  6. Save the property.

To change a view, select its edit button, which opens the same dialog. To delete a view, select its close button.

Build a view's condition

You build the condition from the item's fields. For a list of objects these are the object's fields, such as status or amount. For a list of plain values, the property's own name stands for each item, so a view on a Tags list can say Tags contains "urgent".

Choose a view's fields

Every field starts switched on. At least one always stays shown. A view's condition can still use a field the view hides, so an Open view can filter on Status without showing it.

If none of a view's chosen fields appears in a work item's list, for example because the field was renamed, the view shows every field.

What viewers see

Wherever a work item's list is shown on its own, for example when you open a work item, viewers see one button per view: yours, in the order you added them, then Table and List. Each viewer's choice is remembered for that property in their browser, so it stays the same on every work item. If a viewer never switches, they see the view you chose under Opens on.

In a grid, such as the work items list or a saved report, a list cell shows how many items it holds. If the viewer's chosen view has a condition, the cell counts only that view's items and names it, for example 2 of 5 · Open. Open the work item to switch views.

What a Format does not do

  • It does not change, hide, or delete stored items or fields. Every item and every field is still in the work item, in exports, and in what the AI agent sees.

  • It does not filter work items. A report's filter still selects work items, not the items inside a list.

  • It is not access control. Anyone who can open the work item can switch to Table or List and see every item and field.

Did this answer your question?