Structures, the sheet and saved views
A structure is a named tree of tickets — a portfolio, a release, a team's commitments — built from rules rather than by hand, and shared with the people who need it. The tree is never stored: it is evaluated for each viewer, with that viewer's permissions, so everyone sees only the tickets they may open.
Generators
A structure is built by an ordered generator stack, applied top to bottom, plus any items you place by hand:
| Generator | What it does |
|---|---|
| Insert by TQL | Adds the tickets matching a query, e.g. project = CORE AND type = Epic. |
| Extend by children | Adds each ticket's children beneath it. |
| Group by field | Groups the rows by a field such as assignee, status or a custom field. |
| Filter by TQL | Keeps only the rows that match a query. |
| Sort | Orders rows by a field. |
Ready-made presets get you started, and manual items can be placed and moved anywhere in the tree.
Sharing
| Tier | Can |
|---|---|
| View | Open the structure. |
| Edit | Place and move manual items. |
| Edit generators | Change the generator stack. |
| Control | Rename, share and delete the structure. |
The sheet toolbar
The Sheet view — an editable grid over a project, or over TQL results on the search page — has quick-filter and quick-group chips: pick field values or write a TQL filter, nest groups in chip order, and keep your chips for next time. Saved chips are personal.
Saved views
Saved table and sheet views can be shared with tiers: Use (apply the view), Update (change it) and Manage (share and delete it). Grant a tier to everyone, a user, a user group or a project role. The owner holds Manage, and global admins can manage every view.
Copy to field
A Σ (sum) or formula column in the sheet can be written back into a ticket field. It is preview-first: you see each ticket's old and new value, apply all or a selection, and confirm destructive overwrites. Writes go through the normal ticket update, so permissions, workflow rules and history all apply, and per-ticket failures are reported without stopping the run. Every run is kept in History of copying and can be reverted.