233
edits
Changes
Jump to navigation
Jump to search
Line 10:
Line 10: − + − + − − {| width="100%" − |When you visit [http://bugs.sugarlabs.org bugs.sugarlabs.org], you'll see a webpage with this menu in the top right corner: − If you don't have an account yet, click '''Register''' and create one. If you do have an account, click '''Login''' and sign in to your account. − |[[Image:Trac-login.png|right]] − |} − === Create a new ticket === − {| width="100%" − |Once you log in, the menu on the top right will look like this: − |[[Image:New-ticket.png|right]] − |} − There'll be a button called '''New Ticket''' - click it. You'll end up with a blank ticket, which will look like this: − − [[Image:Blank-ticket.png]] Line 81:
Line 67: − Finally, there's the '''distribution.''' '''For [[Sugar on a Stick]], the distribution is ''[http://fedoraproject.org Fedora]''.''' You can [[wikipedia:Linux_distribution |learn more about what Linux distributions are on Wikipedia]], but this probably isn't the most important information to know - it's just extra information that can help people figure out what's going on.+ − − See [[BugSquad/Status Fields]] for information on the Priority, Milestone, Version, Severity, Bug Status, & Resolution fields. These are usually set by maintainers and [[BugSquad/Triage Guide|Triagers]]. 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. − − [[Image:Soas-bugfiling.png]] − You're almost there! 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.+ − +
no edit summary
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 into Trac ===
=== 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]. If you do not have an existing GitHub account, you can create one by visiting [https://github.com/join]
The first thing you'll have to do is log into our '''ticket system.''' This is a piece of software that keeps track of all our tickets for us. There are many different types of ticket systems; we use [http://trac.edgewall.org/ Trac]. Our instance of Trac is at {{Iframe|http://bugs.sugarlabs.org - go ahead and click that link, or this one: |http://bugs.sugarlabs.org|900|600|1}}
=== Create a summary for the ticket ===
=== Create a summary for the ticket ===
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 ===
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 '''Create Ticket''' button (highlighted in orange) - and then ''poof!'' you've made a ticket.
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!