Changes

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.

 

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.

 

=== 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.

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!