BugSquad/Bug Report: Difference between revisions
No edit summary Tag: visualeditor-switched |
No edit summary Tag: visualeditor-switched |
||
| (One intermediate revision by the same user not shown) | |||
| Line 10: | Line 10: | ||
Tickets are used by [[Development Team|core developers]], [[Activity Team|Activity authors]], organized [[BugSquad/Testing|testers]], and [[Sugar Labs/Getting Involved|anyone]] who wants to help the greater effort! | Tickets are used by [[Development Team|core developers]], [[Activity Team|Activity authors]], organized [[BugSquad/Testing|testers]], and [[Sugar Labs/Getting Involved|anyone]] who wants to help the greater effort! | ||
=== Log | === Log in to GitHub === | ||
The first thing you'll have to do is log in to GitHub, which Sugar Labs uses as its '''ticket system.''' [https://github.com/sugarlabs/sugar/issues]. | The first thing you'll have to do is log in to GitHub, which Sugar Labs uses as its '''ticket system.''' [https://github.com/sugarlabs/sugar/issues]. If you do not have an existing GitHub account, you can create one by visiting [https://github.com/join] | ||
=== Create a summary for the ticket === | === Create a summary for the ticket === | ||
| Line 67: | Line 67: | ||
The next sections we need to look at (highlighted in green) are the '''component''' and '''distribution/OS''' sections. Tickets specify '''components''' to tell us which part of the software or project that we should look at, and who might want to look at it. For instance, if we were working on a bicycle, you might report a bug in the "handlebar" component - that way, we know to just look at the handlebar when we're fixing things, and the people who only want to work on tires know they don't have to worry about that problem. '''For [[Sugar on a Stick]], the component is ''SoaS''.''' | The next sections we need to look at (highlighted in green) are the '''component''' and '''distribution/OS''' sections. Tickets specify '''components''' to tell us which part of the software or project that we should look at, and who might want to look at it. For instance, if we were working on a bicycle, you might report a bug in the "handlebar" component - that way, we know to just look at the handlebar when we're fixing things, and the people who only want to work on tires know they don't have to worry about that problem. '''For [[Sugar on a Stick]], the component is ''SoaS''.''' | ||
As you file and review bugs, you can help triage bugs by finding duplicates and sharing questions and comments with the reporters and maintainers to help advance the work. | |||
=== Create the ticket === | === Create the ticket === | ||
| Line 77: | Line 73: | ||
It's a good idea to preview your ticket before you file it, in order to see what it will look like - click the '''Preview''' button first. You may notice formatting or other problems in the description, so take the time to review your submission because once you create the ticket, the original description can't be modified (only the Summary/Title can be changed). You can always add replies and comments that are tracked chronologically along with other field changes. | It's a good idea to preview your ticket before you file it, in order to see what it will look like - click the '''Preview''' button first. You may notice formatting or other problems in the description, so take the time to review your submission because once you create the ticket, the original description can't be modified (only the Summary/Title can be changed). You can always add replies and comments that are tracked chronologically along with other field changes. | ||
The last thing you should do is click the ''' | The last thing you should do is click the green '''Subnit New Issue''' button. | ||
You're all done for now - congratulations, and thanks for your help! | You're all done for now - congratulations, and thanks for your help! | ||