Every problem has an issue tracker of its own: bad tests, statements that contradict themselves, a checker that rejects a correct answer. Issues are filed on the problem's Issues tab, by console users and by members or testers of the space, and they change nothing about the problem — they are a to-do list attached to it.
The Issues tab is a table sorted by number, newest first. A problem with none reads No issues filed.
Column | Content |
|---|---|
Title | The issue title, or Untitled issue, with its number underneath. |
Status | Open or Closed. |
Assignee | Who is dealing with it. Editable straight in the table. |
Reporter | The console user who filed it, or the space member who did. |
Tags | Free-form labels. Hidden by default. |
Created | When it was filed. Sortable. |
You can filter by Number, Status, Assignee, Reporter and Tags. The tag filter matches exactly, because tags are free-form and there is no fixed vocabulary to pick from.
Report issue opens the create dialog and needs permission to write problems. An issue carries a Title, a Description in rich content — lists, quotes, images, links and code blocks — an Assignee and free-form Tags.
Only the person who reported an issue can write its description. When anyone else edits the issue, the description field is not shown at all and the text is left untouched on save, so a manager retagging or reassigning an issue cannot accidentally rewrite the report.
Edit — problem managers and the issue's own reporter.
Close and Reopen — problem managers only, and each is offered only for the matching status.
Delete — problem managers and the reporter.
Assignee — editable in the table by problem managers and by the reporter; read-only for everyone else.
Clicking an issue opens it: the title with its number, a status badge, the assignee, the age of the issue, then the description and its tags, then the activity feed. The header repeats Edit, Close / Reopen and Delete with the same rules as the table.
The feed opens with a synthesised created this issue entry naming the reporter — or System, where there is none — and then runs through comments and changes: changed status to Closed, assigned this issue to …, removed the assignee.
Comments are written in the box at the bottom of the feed, in the same restricted rich content as descriptions. A comment's author can edit it, and the author or a problem manager can delete it after a confirmation. Editing keeps the format the comment was written in.