Issues and suggestions

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.

Suggestions are a different thing with a similar purpose: a community member proposes an actual replacement for a piece of the problem, and someone reviews it. They exist only in the Basecamp space.

Issues

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.

Filing and editing an issue

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.

Who can do what

  • 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.

The issue page

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.

Suggestions

In the Basecamp space, a problem also has a Suggestions tab. A suggestion is a change proposed by a community member against a published problem, and it alters nothing until someone reviews it. Each suggestion carries exactly one kind of change:

  • a classification change — a different difficulty, and topics;

  • a statement change — a revised title and body for one language;

  • an editorial change — a revised editorial for one language.

The table shows the member who proposed it, when they last updated it, and its status: Pending, In review, Approved or Rejected. You can filter by status.

Reviewing a suggestion

Clicking a row, or Review in its menu, opens the review overlay, which puts the proposal next to what the problem currently has — current title against suggested title and current body against suggested body for a statement change, with the language named above; current against suggested editorial; current against suggested difficulty. Both sides are read-only.

A pending suggestion gets Approve and Reject. Approve asks for confirmation and applies the change. Reject offers an optional comment for the author. A suggestion that is no longer pending offers only Close.

Rejecting keeps the suggestion, so its author can revise it and put it back in the queue. Delete, from the row menu, removes it outright and leaves no record.

A suggestion also records the problem version it was written against, so an old suggestion may not apply to the problem as it now stands — worth checking before approving one that has been sitting for a while.

On the participant side, the entry points that create suggestions — report a problem, leading to topic, statement, translation or editorial suggestions — are shown only to signed-in members of the Basecamp space.