Features · Structures
Structures: ticket trees for planning and portfolios
Shareable hierarchies built from TQL, saved views with real sharing, and a sheet that writes computed values back.
A structure is a named tree of tickets — a portfolio, a release, a programme — built from a stack of rules instead of by hand: insert tickets by TQL, extend them with their children, group, filter and sort, then place anything else manually. Share it with View, Edit, Edit generators or Control rights. Each viewer sees the tree through their own permissions, so one structure serves the whole organisation.
What you get
- Generators, not copy-paste — Insert by TQL, Extend by children, Group by field, Filter by TQL and Sort — stacked in order, re-evaluated every time the structure opens.
- Manual items too — place and move items anywhere in the tree when a rule can't express it.
- Four sharing tiers — View, Edit, Edit generators and Control, granted per structure.
- Quick filters and groups — chips on the sheet toolbar filter by field values or TQL and nest groups, saved per user.
- Saved views you can share — Use, Update and Manage tiers, granted to everyone, users, groups or project roles.
- Copy to field — write a Σ or formula column back into ticket fields — previewed first, applied through normal ticket updates, every run kept and revertible.
Evaluated per viewer
The tree is never stored. Each time someone opens a structure, its generators run with that person's visibility, so a structure shared across teams never shows a ticket a viewer could not open on its own. Restricted tickets stay out, project membership is respected, and the same structure can safely be shared with people who see different slices of the work.
Write-back without surprises
Copy to field starts with a preview of every ticket's old and new value. Apply everything or a selection; destructive overwrites ask first. Each write goes through the ordinary ticket update path — permissions, workflow, history, live events — and the run is kept in a history you can revert from.
A portfolio in three generators
Insert by TQL type = Epic AND fixVersion = "2026.4"
Extend by children
Group by field teamSee Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.