​

saved-views

orc saved-views saves a named JSON query-filter object and lists saved views. Use it to retain filters for reusing the same conditions.

CLI authentication and a selected Workspace are required. These are separate resources from orc issues views, which manages Issue layouts and shared defaults. Filter keys are not validated against report query parameters when saved; clients interpret them when applying the view.

List saved filters.

Lists query-filter views saved in the current Workspace. Use --limit and --cursor for pagination.

Saves a view using name and a JSON object in filter. Names contain 1–120 characters after trimming. Send a complete JSON resource with --stdin to preserve nested filters.

Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.

Type: string. Optional.

(required) Display name, trimmed on creation. Contains 1–120 characters after trimming.; max 120 chars

Type: string. Optional.

(required) Stored query-filter object. Keys are not validated against report query parameters when saved; clients interpret the object when applying the view.; (JSON object, e.g. '{"custom_id":"x"}')

Type: string. Optional.

Save a named filter from a file.

See Manage measurement configuration and saved filters for combining measurement settings with saved conditions.

The following global options can be used with orc saved-views:

For details and examples, see global options.