Skip to main content

IssueFrameRange Objects

Represents a range of frames [start, end] inclusive

SceneCoordinateIssue Objects

Issue anchored to a 3D coordinate within a scene on a specific frame.

FrameRangeIssue Objects

Issue anchored to a range of frames

AnnotationIssue Objects

Issue anchored to a specific annotation (label rejection or annotation feedback)

TaskIssues Objects

list

Lists all issues (comment threads) for this task. Returns an iterator of issues anchored to different parts of the data unit:
  • FileIssue: Issues anchored to the entire data unit
  • FrameIssue: Issues anchored to a specific frame
  • CoordinateIssue: Issues anchored to specific 2D coordinates on a frame
  • SceneCoordinateIssue: Issues anchored to 3D scene coordinates on a frame
  • FrameRangeIssue: Issues anchored to a range of frames
  • AnnotationIssue: Issues anchored to a specific annotation
Each issue includes comments, tags, and resolution history. Returns:
  • Iterable[Issue] - An iterator of Issue objects (discriminated union of all issue types).
Example:

add_file_issue

Adds a file issue. Arguments:
  • comment str - The comment for the issue.
  • issue_tags List[str] - The issue tags for the issue.
  • space_id Optional[str] - For data units that use spaces (Data Groups and scenes), identifies which space the issue is attached to. Leave as None for data units without spaces.

add_frame_issue

Adds a frame issue. Arguments:
  • frame_index int - The index of the frame to add the issue to.
  • comment str - The comment for the issue.
  • issue_tags List[str] - The issue tags for the issue.
  • space_id Optional[str] - For data units that use spaces (Data Groups and scenes), identifies which space the issue is attached to. Leave as None for data units without spaces.

add_coordinate_issue

Adds a issue pinned to a coordinate. Arguments:
  • frame_index int - The index of the frame to add the issue to.
  • x float - The x coordinate of the issue.
  • y float - The y coordinate of the issue.
  • comment str - The comment for the issue.
  • issue_tags List[str] - The issue tags for the issue.
  • space_id Optional[str] - For data units that use spaces (Data Groups and scenes), identifies which space the issue is attached to. Leave as None for data units without spaces.

add_scene_coordinate_issue

Adds an issue pinned to a 3D coordinate in a scene on a specific frame. Arguments:
  • frame_index int - The index of the frame to add the issue to.
  • x float - The x coordinate (in scene space).
  • y float - The y coordinate (in scene space).
  • z float - The z coordinate (in scene space).
  • comment str - The comment for the issue.
  • issue_tags List[str] - The issue tags for the issue.

add_annotation_issue

Adds an issue anchored to a specific annotation (object or classification instance). Arguments:
  • annotation_id str - The annotation the issue is attached to. This is the object instance object_hash (or classification instance classification_hash) of the annotation within this task’s data unit.
  • comment str - The comment for the issue.
  • issue_tags List[str] - The issue tags for the issue.
  • frame_ranges Optional[List[IssueFrameRange]] - The frame ranges to pin the issue to, each an inclusive [start, end] range. Leave as None to flag the whole annotation instance across every frame it appears on (e.g. a wrong attribute value). Provide one or more ranges to target the instance on those frames (e.g. a bad contour over a span of frames). A single frame is a range where start == end.
  • space_id Optional[str] - For data units that use spaces (Data Groups and scenes), identifies which space the annotation belongs to. Leave as None for data units without spaces.
Example:
Raises:
  • ValueError - If frame_ranges is an empty list (omit it, or pass None, to target the whole annotation instance) or contains an invalid range where start is negative or start > end.

delete

Deletes one or more issues from this task in a single request. Accepts either Issue objects (as returned by list()) or raw UUIDs, mixed freely. Empty input is a no-op. Permissions: project admins can delete any issue. Issue authors can delete their own general issues, but annotation issues (label rejections) can only be deleted by project admins. The back-end validates the entire batch before deleting anything: if any issue cannot be deleted (because the caller is not the author and not a project admin, or the issue doesn’t belong to this task’s project), the request raises and NO issues in the batch are deleted. Arguments:
  • issues - A list of Issue objects or UUIDs to delete.
Example: