-
Notifications
You must be signed in to change notification settings - Fork 10
issue_tracker
Stuart Spence edited this page Mar 26, 2016
·
2 revisions
#Issue Tracker
Here is a link to all the "issue tickets" in our VR project. You can search in many useful ways. For example: here's a link to all issues tagged with "help wanted". Here's a link to all the feature requests (new ideas) for the game.
###What is an issue?
An issue can be a bug, new idea for the game (feature), or question. All tickets require someone to take some action.
###How do I suggest a new idea?
You need to create a new issue. All ideas or feature requests should have the label "type:feature". If you can, add a task type too. If this is a programming request, add the label "task:programming".
###How do I write a bug report?
You need to create a new issue. All bugs must have two things:
- Reproduction steps. Be very clear about what you did to make this bug happen. If a programmer cannot reproduce your bug, it won't get fixed. If you know how, include what version of the game (or commit hash) you used.
- Expected result and actual result. What did you expect to happen? What actually happened?
###Tips
- If you want to catch someone's attention with a ticket, add them as an assignee. They'll get notifications about this ticket.
- You should add a priority label to all tickets. If you don't know what priority to add, set it to "priority:low".
- When a ticket is resolved, completed, or rejected, "close" it!