Issues

• Every time a label is rejected, a label rejection issue is created.
• Other Issues can be created, relating to the entire data unit, or on a specific part of a data unit.
• Issue tags can be used to categorize and filter issues.

​

Issue Tags

​

Create Issue Tags

1. Click Settings in the My workspace section. The Users page appears.
2. Navigate to the Issue Tags tab. The Issue Tags page appears.
3. Click + New issue tag to create a new issue tag for your Workspace.
4. Give your Issue Tag a meaningful name and press ENTER to create the Issue Tag.
5. Repeat Steps 3 and 4 to create as many Issue Tags as necessary.

​

Delete Issue Tags

1. Click the delete icon next to the issue tag you want to remove.
2. Confirm the deletion when prompted.

1. Select the checkboxes next to the issue tags you want to delete.
2. Click the Delete selected button that appears.
3. Confirm the bulk deletion when prompted.

​

Add Issue Tags to Projects

1. Navigate to your annotation Project.
2. Navigate to the Settings tab.
3. Click the dropdown in the Issue tags section.
4. Select, or type the name of, the issue tag you want to add to the Project.

5. Apply Issue Tags when creating issues, or when managing issues in the Issues tab of your Project.

​

Working with Issues

​

Create Issues

[Reviewer] Create Label Rejection Issues

1. Open a review task from the Queue tab of your annotation Project.
2. Reject a label. The Issues pane opens.
3. Select any Issue Tags you want to apply to the issue.
4. Add a comment explaining why the label is being rejected.
5. Click Reject to create the label rejection Issue.

6. Click Reject task to reject the task.

[Annotator / Reviewer] Create Other Issues

1. Open a task from the Queue tab of your annotation Project.
2. Open the Issues pane by clicking the Issues icon.
3. For data groups with multiple tiles, select the specific tile the issue applies to using the tile selector dropdown.
4. Click the New issue icon (or keyboard shortcut Ctrl+N).
5. Click the Apply to dropdown to select the type of issue you want to create.
6. Select any Issue Tags you want to apply to the issue.
7. Add a comment to the issue.
8. If you selected ‘Pin on canvas’ in Step 5, click the desired location on the canvas.
9. Click Create issue.

​

Resolve Issues

1. Open a task from the Queue tab of your annotation Project. Rejected tasks The Label Editor with the Issues pane already opened appears.
2. Address the problem raised by the Issue.
3. Add a reply to the Issue acknowledging the issue has been addressed.
4. Resolve the Issue by clicking the tick icon on the thread.

​

Data Group Issues

• View issues specific to each tile
• Create issues that apply to a particular tile
• See validation warnings for missing required annotations across all tiles

​

Multi-Tile Validation

• Per-tile validation: Required classifications and attributes are checked on each tile separately
• Visual indicators: The Issues panel shows which tiles have missing required annotations
• Tile-specific issues: Missing annotation issues are created for the specific tile where they’re absent

​

Managing Issues

​

Comment Threads & Activity

• The Discussion tab allows new comments to be added, and issues to be resolved.
• The Activity tab shows all actions taken on the issue, including when it was created, resolved, reopened, and any comments added.

​

Filter Issues

• Priority: Low, Medium, High, or All
• Source: The source of the issue, such as Label Rejection.
• Status: Open, Resolved, or All
• Updated: When was the Issue last updated.
• Raised by: The user who created the issue.
• Assigned to: The user the issue is assigned to.
• Tags: The Issue tags applied to the issue.
• Class: The Ontology class the issue relates to.
• Stage: The Workflow stage the issue relates to.

​

Bulk Issues Actions

• Assign: Assign the selected issues to a specific user.
• Release: Release the selected issues from their current assignee, making them unassigned.
• Change priority: Update the priority level of the selected issues.
• Move: Move the selected issues to a different Workflow stage.

​

Issue Analytics

1. Navigate to the Analytics tab of your Project.
2. Navigate to the Issues section. Analytics pertaining to Issues appear.

• Total issues created: The total number of issues created.
• Total issues resolved: The number of issues marked as resolved.
• Total issues reopened: The number of issues that were reopened.

• Total issues created = 19
• Total issues resolved = 20
• Total issues reopened = 2

• 19 issues were created.
• All 19 issues were resolved.
• 2 resolved issues were reopened. (This includes manually reopening an issue and re-rejections of labels)
• 1 of the reopened issues was resolved.
• There is one remaining open issue.

​

Creating Issues With Agents

from encord import EncordUserClient
from encord.workflow import AgentStage

# User input
SSH_PATH = "<private_key_path>"  # Replace with the file path to your SSH private key
PROJECT_ID = "<project_id>"      # Replace with the unique Project ID
AGENT_STAGE_NAME = "<agent_stage_name>"  # Replace with the name of your Agent stage

# --- Connect to Encord ---
user_client = EncordUserClient.create_with_ssh_private_key(
    ssh_private_key_path=SSH_PATH,
    # For US platform users use "https://api.us.encord.com"
    domain="https://api.encord.com",
)

# Get Project and Workflow
project = user_client.get_project(PROJECT_ID)
workflow = project.workflow

# Get the Agent stage and iterate over its tasks
agent_stage = workflow.get_stage(name=AGENT_STAGE_NAME, type_=AgentStage)
for task in agent_stage.get_tasks():

    # List all existing issues on the task
    existing_issues = list(task.issues.list())
    print(f"Task {task.uuid} has {len(existing_issues)} existing issue(s)")

    # Add a file-level issue (applies to the entire data unit)
    task.issues.add_file_issue(
        comment="File is corrupted or unreadable",
        issue_tags=["<issue_tag>"],  # one or more issue tags configured in your Project
    )

    # Add a frame-level issue (applies to a specific frame)
    task.issues.add_frame_issue(
        frame_index=0,
        comment="Motion blur makes annotation impossible on this frame",
        issue_tags=["<issue_tag>"],  # one or more issue tags configured in your Project
    )

    # Add a coordinate-level issue (applies to a specific location within a frame)
    task.issues.add_coordinate_issue(
        frame_index=0,
        x=0.5,
        y=0.5,
        comment="Ambiguous object boundary at this location",
        issue_tags=["<issue_tag>"],  # one or more issue tags configured in your Project
    )

    print(f"Issues added to task {task.uuid}")