User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cppdev:submittickets [2010-01-14 00:18] Carsten Updated text about login sharing. |
cppdev:submittickets [2017-02-05 17:15] Carsten deleted obsolete page (it's all done via the Bitbucket Issue Tracker now) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| In order to create a new ticket, you must [[http://trac.cafu.de/login|login to Trac]] first. | In order to create a new ticket, you must [[http://trac.cafu.de/login|login to Trac]] first. | ||
| - | (The Trac login is connected to the forum database: You only have to register once at the [[http://www.cafu.de/forum/|forums]], where your account is managed and kept. Login with the same username and password at Trac, then check in the [[http://trac.cafu.de/prefs|Preferences]] if your email address has been overtaken into the Trac session correctly.) | + | If this is your first visit to Trac, note that the Trac login is connected to the forum database: You only have to register yourself once at the [[http://forum.cafu.de|forums]], where your user account is managed and kept. Login with the same username and password at Trac, then check in the [[http://trac.cafu.de/prefs|Preferences]] if your email address has been overtaken into the Trac session correctly. Optionally fill in your full name as well. |
| - | Before creating a new ticket, //use the search functions// in order to make sure that the bug or proposed enhancement is not already submitted: | + | Before creating a new ticket, //use the search functions// in order to make sure that the bug or proposed enhancement has not already been submitted: |
| * Use the [[http://trac.cafu.de/search?ticket=on|search]] for global search. | * Use the [[http://trac.cafu.de/search?ticket=on|search]] for global search. | ||
| * Use //queries// to search for strings | * Use //queries// to search for strings | ||
| * in ticket summaries (example: [[http://trac.cafu.de/query:status!=closed&summary~=soundsys]]) or | * in ticket summaries (example: [[http://trac.cafu.de/query:status!=closed&summary~=soundsys]]) or | ||
| - | * in ticket lists of keywords (example: [[http://trac.cafu.de/query:status!=closed&keywords~=SoundSys]]). | + | * in ticket keywords (example: [[http://trac.cafu.de/query:status!=closed&keywords~=SoundSys]]). |
| If you are unsure whether you encountered the same bug, open a new ticket and add mutual links to both tickets | If you are unsure whether you encountered the same bug, open a new ticket and add mutual links to both tickets | ||
| - | (entering a ticket number like ''#1234'' into a ticket description is automatically converted into a hyperlink to ticket number 1234). | + | (entering a ticket number like ''#1234'' into a ticket description is automatically converted into a hyperlink to ticket number 1234). |
| - | If you want to express interest in a bug that is already submitted, add yourself to the CC list or add more details. Or even better, try to fix it. | + | If you want to express interest in a bug that is already submitted, add yourself to the CC list or add more details. Or even better, try to fix it. ;-) |
| When reporting a bug, it's usually obvious to the submitter (you) what the problem is. Unfortunately it's quite often less obvious to us (the developers) and the chances of a bug being fixed decrease dramatically if we can't even understand what it is. So please follow this general template when reporting the bugs, with the possible exception of really trivial and self-explanatory ones: | When reporting a bug, it's usually obvious to the submitter (you) what the problem is. Unfortunately it's quite often less obvious to us (the developers) and the chances of a bug being fixed decrease dramatically if we can't even understand what it is. So please follow this general template when reporting the bugs, with the possible exception of really trivial and self-explanatory ones: | ||
| Line 35: | Line 35: | ||
| Provide a concise and meaningful title. | Provide a concise and meaningful title. | ||
| You may assume that the **Summary** field will be viewed together with **Type** and **Component**. | You may assume that the **Summary** field will be viewed together with **Type** and **Component**. | ||
| - | For example, you don't need to mention ''CaWE'' in the summary if the component is set to ''CaWE''. | + | For example, you don't need to mention "CaWE" in the summary if the component is set to ''CaWE''. |
| === Description === | === Description === | ||
| Line 43: | Line 43: | ||
| === Priority === | === Priority === | ||
| - | Please be very conservative with the priority setting, ''normal'' is almost always right. | + | Please be very conservative with the priority setting, ''normal'' is almost always right. ;-) |
| === Component === | === Component === | ||
| Line 57: | Line 57: | ||
| === CC === | === CC === | ||
| - | The ticket reporter is always notified about changes, so there is no need to add yourself to the **CC** list. | + | The [[http://www.cafu.de/support/mailing-lists|cafu-dev mailing list]] is always notified about new ticket creations and ticket changes. Therefore, we recommended that you subscribe to cafu-dev for keeping informed about all changes. |
| - | Use this field when you are interested in a ticket opened by somebody else. | + | |
| + | If you prefer to not subscribe to cafu-dev but want to get email notifications about changes to this ticket, add yourself to the **CC** list. This works both with tickets opened by you or by somebody else. | ||
| === Platform === | === Platform === | ||
| Line 85: | Line 86: | ||
| Any of these typically just has the opposite effect: A developer has to spend time with re-setting or fixing the ticket, slowing things down. | Any of these typically just has the opposite effect: A developer has to spend time with re-setting or fixing the ticket, slowing things down. | ||
| */ | */ | ||
| + | |||
| + | |||
| + | ===== Ticket Workflow ===== | ||
| + | |||
| + | {{ :cppdev:cafuticketworkflow.png?240|The Cafu ticket workflow.}} The diagram at the right presents the states that a ticket can be in, and the transitions that indicate how a ticket changes from one state into the next. | ||
| + | |||
| + | The first state of a new ticket is always **new**, and it is up the developers to initiate transitions to other states. When a ticket has reached state **closed**, its objectives have been met and its issue is being considered resolved. | ||
| + | |||
| + | The source file of the diagram is {{:cppdev:cafuticketworkflow.dia}}, and another version that has been automatically generated with GraphViz is [[http://docs.cafu.de/_media/cppdev:cafuticketworkflow-graphviz.png|here]]. | ||
| ===== Final Note ===== | ===== Final Note ===== | ||
| - | Cafu is to a large degree a community project, and we need and very much appreciate your help. | + | Cafu is, to a large degree, a community project, and we need and very much appreciate your help. |
| Here are just a few examples on what you can do: | Here are just a few examples on what you can do: | ||
| Line 96: | Line 106: | ||
| * We really welcome other help with the existing bugs as well: for example, verifying that the bugs can still be reproduced, commenting on potential workarounds and so on. | * We really welcome other help with the existing bugs as well: for example, verifying that the bugs can still be reproduced, commenting on potential workarounds and so on. | ||
| - | Looking forward to your tickets! :-D | + | We're looking forward to your tickets! :-D |