This guide explains how to use the Issues feature in Encord. Each step in the process is intended for a specific user role, which is indicated in the heading of that step.
This guide assumes you have already added data into Encord and set up your annotation Projects.

​
STEP 1: [Org Admin] Create Issue Tags

Issue tags can be created in the Organization Settings by Org admins, or the Project Settings by Project admins.
For more information, refer to our Issue Tags documentation.
Issue tags serve as a system to categorize, group, and filter issues within Projects.
  1. Click Settings in the My organization 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 Organization.
  1. Give your Issue Tag a meaningful name and press ENTER to create the Issue Tag.
  2. Repeat Steps 3 and 4 to create as many Issue Tags as necessary.

​
STEP 2: [Admin] Add Issue Tags

  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.

​
STEP 3: [Annotator / Reviewer] Create Issues

For more information, refer to the Issues documentation.
Issues cannot be created in a Consensus annotate stage.

​
STEP 4: [Annotator / Reviewer] Resolve Issues

More information can be found in the Issues documentation.
  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.

​
STEP 5: [Project Admin / Team Manager] Issue Analytics

The number of issue actions taken by each Project collaborator can be viewed in the Collaborators tab.
  1. Navigate to the Analytics tab of your Project.
  2. Navigate to the Issues section. Analytics pertaining to Issues appear.
ChartDescription
Issue actionsShows the number of issues created, resolved, and opened.
Issue tag occurrenceShows the count of all issue tags used within the chosen timeframe.
Issue tag occurrence by classShows the actions taken for all objects and classifications in the Ontology.
The Issue actions chart shows the following:
  • 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.
Example - How to Understand Issue Analytics: If your Issue actions chart shows:
  • Total issues created = 19
  • Total issues resolved = 20
  • Total issues reopened = 2
This means that:
  • 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.