Create a shared saved view
Requires Admin access. Adds one view after the existing shared views, visible to every project member. Sets its structure (start type and nesting rules, by data type id) and optionally its table columns, filters and sort, each checked against the data model; display options are edited in Flow. An id that is already a shared view answers 409.
Authorizations
Headers
Workspace identifier
Path Parameters
Body
Table columns, in order. Replaces every column; [] leaves the view on the default columns. Stored as state.columns.
Conditions every item the view shows must meet, joined by operator; a group node joins its own nodes with its own operator. Each leaf's type is the FIELD'S DATA TYPE (tag, stage, verificationResult, text, richText, number, date, toggle, user, presence) with fieldId a field key from the categories endpoint (or <typeId>::<key>), or a structural condition (type, linkedTo, timestamp, changedInBranch, the comment conditions). Tag, stage and verification values are option NAMES; user values are user ids; type ids are data type ids. Unknown fields, options, types or operations answer 400 and nothing is saved. Example — Status is Triage: {"operator":"and","nodes":[{"type":"tag","fieldId":"status","operation":"overlaps","tags":["Triage"]}]}. Stored as state.filters.
Id for the new view: letters, digits, ., _ and -, starting with a letter or digit. Supply one so a retry of an unknown outcome can be checked by reading it; omitted, Flow picks one.
Nesting rules, in order: under each parentType, show items of childType. Replaces every rule; send [] to remove them all. Stored as state.relationships.
Data type id of the items the view starts from (its "Start type"). Stored as state.rootType.
Ordered sort keys, the first most significant. Replaces the whole sort; send [] for the natural order. Stored as state.sort.