MongooseA text-based world full of questionable inventions.

All help topics · Link to this topic

Showing help on '@issue'

@issue - report a problem and follow up on it

@issue <what is wrong> files a report. Describe what you did, what happened, and what you expected. Your room, client and last 20 commands are attached automatically.
@issue lists your reports. Replace N below with an issue number, without the #.
@issues lists and searches every issue you can read: all issues past status new, and your own new reports. See help @issues.
@issue N shows a report you may read: its details, current notes and status changes. Attached held items, recent commands and tracebacks are summarized in one line.
@issue N context shows that attached context in full. @issue N history shows the full history, including each note as first written.
@issue N note <text> adds a note. @issue N <text> also adds a note.
Example: @issue 65 note It happens when I request tea.
@issue N edit-note M <text> replaces note M's current text. @issue N remove-note M removes it from the current discussion.
Read @issue N to find each note's number. Numbers stay the same after edits and removals, and may have gaps.
Only a note's author or a wizard can edit or remove it, and the issue must still be readable to them.
Previous text, authors and edit/removal times remain readable with @issue N history. Removing a note does not erase it or allow it to be restored.
Example: @issue 65 edit-note 2 It happens only when I request tea twice.
@issue N reply M <text> adds a new note replying to note M. Replies show which note they answer, and can themselves be answered, edited or removed.
Example: @issue 65 reply 2 I can reproduce this with coffee too.
@issue N followup <summary> files a new, unassigned issue for something found while working on issue N. Both issues' histories record the link. Example: @issue 112 followup bf_add_property announces each change twice
Anyone who can read an issue can add notes or replies. Reply links remain valid when the original note is edited or removed.
New notes and replies notify previous note authors once each, excluding the person posting and anyone who can no longer read the issue. Connected players receive a notice; offline players receive MOO mail. Editing or removing a note does not send a new-note notice.

Wizard commands
Wizards can read and manage any issue, including new ones. help @issues explains browsing and searching.
@issue N status <status> changes status.
Statuses: new, open, claimed, blocked, review, done, duplicate, wontfix.
Example: @issue 65 status open
@issue N area <area> sets the area.
Areas: client, sound, world, server, web, docs, other.
@issue N kind <kind> sets the kind: report, todo, bug, idea.
@issue N priority <priority> sets priority: low, medium, high, emergency.
@issue N assign me assigns it to you. Use assign <player> to assign someone else, or assign none to clear the assignment.
@issue N dup M marks N as a duplicate of issue M and adds a link to M's history.
@issue N dispatch <backend> [model] launches an agent to investigate. Omit [model] to use the backend's default model. Dispatch changes status to claimed and assigns the issue to you.
Done, duplicate and wontfix issues cannot be dispatched.

Ideas for improving the issue system itself go on issue #115: @issue 115 note <what you were doing and what would have helped>.
See also: help @issues, help report