subroutine view
The 5 commands under subroutine view, each with its arguments and options.
subroutine view [OPTIONS] COMMAND [ARGS]...
Save a narrowing under a name, and come back to it.
subroutine view list
subroutine view list [OPTIONS]
Show the views you saved and the ones shared with this workspace.
Examples:
subroutine view list
Each row is the name you type to run it, how it is drawn, what it narrows to, whose it is, and whether the workspace can see it. A view is yours until you share it.
Options
--json(flag): Print the list as JSON.
subroutine view run
subroutine view run [OPTIONS] [key]
Show the work a saved view selects.
Examples:
subroutine view run my-bugs
subroutine view run my-bugs --order -created_at
A terminal honours what a view narrows to and draws a list. A view saved as a board or an agenda, or grouped, says so on the line above the rows rather than quietly coming back as something else.
Arguments
key(str): Which view, by its name.
Options
--limit(int, default50): How many to show.--json(flag): Print the results as JSON.--merged(flag): One list rather than a group per connection.--strict(flag): Stop if any connection cannot be reached.--order(str): Sort by this instead of the order the view saved.--project(str, repeatable): Only this project, by key.--tag(str, repeatable): Only what carries this tag, without the '#'.--connection(str): Only this connection, by name.--deferred(flag): Include what you have deferred until a later date.--filter(str, repeatable): Narrow by a field — 'importance.gte=4', 'tag.in=ops,web', 'assignee.is=unset', 'created_at.gte=yesterday'. Repeat to narrow further: a range, or one field twice.
subroutine view save
subroutine view save [OPTIONS] [title]
Save a narrowing under a name, so nobody has to retype it.
Examples:
subroutine view save "My bugs" --q "type:bug assignee:me"
subroutine view save "Team queue" --q "urgency>=4" --as board --shared
The name you type it by is made from the title, so "My bugs" answers to 'my-bugs'. A view is yours until you say --shared, so forgetting publishes nothing.
Arguments
title(str): What to call it, in one line.
Options
--q(str): What it narrows to. See 'explain searching'.--as(str, default'list'): How it is drawn: agenda, list, board.--order(str): Sort by, e.g. '-priority_score'.--group-by(str): Group by this, where it is drawn.--shared(flag): Let the whole workspace see it. Yours alone otherwise.--json(flag): Print the result as JSON.
subroutine view edit
subroutine view edit [OPTIONS] [key]
Change a view you saved.
Examples:
subroutine view edit my-bugs --q "type:bug urgency>=4"
subroutine view edit team-queue --shared
subroutine view edit team-queue --group-by ""
Only the parts you name change. Writing nothing after --q, --order or --group-by clears that part, which is a different instruction from leaving the flag off.
Arguments
key(str): Which view, by its name.
Options
--title(str): Rename it. This changes its name too.--q(str): What it narrows to. Empty clears it.--as(str): How it is drawn: agenda, list, board.--order(str): Sort by. Empty clears it.--group-by(str): Group by. Empty clears it.--shared / --private(flag): Show it to the workspace, or take it back.--json(flag): Print the result as JSON.
subroutine view forget
subroutine view forget [OPTIONS] [key]
Remove a view you saved, for good.
Examples:
subroutine view forget my-bugs
There is no trash for a view, unlike a task: it records nothing that happened, and one left behind would hold its name against whoever wants it next.
Arguments
key(str): Which view, by its name.