Issue Tracker Guidelines » History » Version 6
Nuika Sanders, 05/22/2015 02:19 PM
| 1 | 1 | I. Lazaridis | h1. Issue Tracker Guidelines |
|---|---|---|---|
| 2 | |||
| 3 | |||
| 4 | h2. Scope |
||
| 5 | |||
| 6 | 6 | Nuika Sanders | The main scope of the Issue Tracker is to assist wt developers in their daily work, and to provide the users of wt the means for precise feedback on wt. "www":http://amodaa.ru/ |
| 7 | 1 | I. Lazaridis | |
| 8 | |||
| 9 | h2. Developers |
||
| 10 | |||
| 11 | 4 | I. Lazaridis | * Do not reject issues immediately, except you are 100% sure. It can make the project look rude and more. |
| 12 | ** Another user can find the open issue (e.g. a feature request) and suggest a way to implement it. |
||
| 13 | 1 | I. Lazaridis | ** See e.g. #2857, the developer should have asked additionally for the reasons, instead of "rejecting" immediately. |
| 14 | * Do not leave old issues (e.g. older than a year) unprocessed. |
||
| 15 | |||
| 16 | h2. Users |
||
| 17 | |||
| 18 | 2 | I. Lazaridis | * You file new Issues with the "New issue":/projects/wt/issues/new entry in the main menu |
| 19 | 1 | I. Lazaridis | * Create an account, thus you have the benefit of having a list of your issues. |
| 20 | 5 | I. Lazaridis | * If you are not sure if you should file and issue, open a topic on the forum and discuss your issue. |
| 21 | 1 | I. Lazaridis | * Express yourself clearly and give context and version information |
| 22 | * If your issue was closed or rejected, do not file a new one |
||
| 23 | ** You can still comment on a closed/rejected issue. |
||
| 24 | ** You can open a topic on the forum and discuss the issue with other users. |
||
| 25 | * File one Issue for each Bug/Feature/Request you have (do not combine them) |
||
| 26 | ** Negative Example: #2856 |