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-02-23 17:40] Carsten Revised text about CC field after changes to trac.ini |
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. | ||
| - | 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://www.cafu.de/forum/|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. | + | 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 has not already been 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: | ||
| Line 19: | Line 19: | ||
| * in ticket 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. ;-) | ||
| Line 57: | Line 57: | ||
| === CC === | === CC === | ||
| - | 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. 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. | + | 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. |
| + | |||
| + | 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 84: | 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: | ||