BugSquad/Bug Report: Difference between revisions

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!

=== Log into ~~Trac~~ ===

=== Log into 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 ~~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}}~~

~~{| 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]]~~

=== Create a summary for the ticket ===

Line 89:

Line 75:

=== Create the ticket ===

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

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.

@@ 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!
-=== Log into Trac ===
+=== Log into 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 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}}
-{| 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]]
 === Create a summary for the ticket ===
@@ Line 89: / Line 75: @@
 === Create the ticket ===
-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.
+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.