BugSquad/Bug Report - Revision history

MrBIOS at 18:41, 6 June 2019

2019-06-06T18:41:39Z

← Older revision		Revision as of 14:41, 6 June 2019
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 ~~into~~ GitHub ===		=== 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 ===

MrBIOS at 18:37, 6 June 2019

2019-06-06T18:37:06Z

← Older revision		Revision as of 14:37, 6 June 2019
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''.'''

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

	~~[[Image:Soas-bugfiling.png]]~~

	=== 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 '''~~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!

MrBIOS at 18:35, 6 June 2019

2019-06-06T18:35:01Z

← Older revision		Revision as of 14:35, 6 June 2019
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 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 ===		=== Create a summary for the ticket ===
Line 89:		Line 75:
	=== Create the ticket ===		=== 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.		The last thing you should do is click the '''Create Ticket''' button (highlighted in orange) - and then ''poof!'' you've made a ticket.

FGrose: expand context of developers

2010-09-17T15:13:07Z

expand context of developers

← Older revision		Revision as of 11:13, 17 September 2010
Line 6:		Line 6:
	== How to file a ticket ==		== How to file a ticket ==

	If you're using [[Sugar on a Stick]] or another [[Supported systems\|distribution of Sugar]] and find something specific you think could be improved—maybe something isn't working the way you think it should work, or you have an idea for how something could be better—you can file a '''ticket.''' A ticket is a way for anyone to suggest to the software or project ~~developers~~ that they should work on something.		If you're using [[Sugar on a Stick]] or another [[Supported systems\|distribution of Sugar]] and find something specific you think could be improved—maybe something isn't working the way you think it should work, or you have an idea for how something could be better—you can file a '''ticket.''' A ticket is a way for anyone to suggest to the software or project development community that they should work on something.

	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!
Line 29:		Line 29:
	=== Create a summary for the ticket ===		=== Create a summary for the ticket ===

	You'll notice that the first text box is for a '''Summary''' of the ticket. Sometimes the '''Summary''' is also called the '''Title''' of the ticket. This is an important part of the ticket—in fact, some people say it is the ''most'' important part—because reading the title of a ticket is how ~~a developer~~ decides if he or she is going to work on it.		You'll notice that the first text box is for a '''Summary''' of the ticket. Sometimes the '''Summary''' is also called the '''Title''' of the ticket. This is an important part of the ticket—in fact, some people say it is the ''most'' important part—because reading the title of a ticket is how someone decides if he or she is going to work on it.

	Write a ticket summary/title that describes your idea. Try to write it succinctly, so that ~~a developer~~ reading the title of your ticket will go "oh, I know what I have to work on, and why this is important - I will read more about this ticket and maybe try to fix it."		Write a ticket summary/title that describes your idea. Try to write it succinctly, so that those reading the title of your ticket will go "oh, I know what I have to work on, and why this is important - I will read more about this ticket and maybe try to fix it."

	A good ticket is in many ways like a good newspaper headline.		A good ticket is in many ways like a good newspaper headline.
Line 81:		Line 81:
	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''.'''

	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 ~~developers~~ figure out what's going on.		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.		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.

FGrose at 05:57, 27 May 2010

2010-05-27T05:57:29Z

← Older revision		Revision as of 01:57, 27 May 2010
Line 1:		Line 1:
	</noinclude>{{TeamHeader\|BugSquad}}{{TOCright}}		</noinclude>{{TeamHeader\|BugSquad}}{{TOCright}}
			[[Category:HowTo]]
	[[Category:Testing]]		[[Category:Testing]]
	[[Category:Sugar on a Stick]]		[[Category:Sugar on a Stick]]

Mchua at 14:13, 22 May 2010

2010-05-22T14:13:25Z

← Older revision		Revision as of 10:13, 22 May 2010
Line 1:		Line 1:
	</noinclude>{{TeamHeader\|BugSquad}}{{TOCright}}		</noinclude>{{TeamHeader\|BugSquad}}{{TOCright}}
	[[Category:Testing]]		[[Category:Testing]]
			[[Category:Sugar on a Stick]]
	</noinclude>		</noinclude>
	== How to file a ticket ==		== How to file a ticket ==

FGrose at 05:07, 14 April 2010

2010-04-14T05:07:31Z

← Older revision		Revision as of 01:07, 14 April 2010
Line 10:		Line 10:
	=== Log into Trac ===		=== Log into Trac ===

	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 {{~~Show~~\|http://bugs.sugarlabs.org - go ahead and click that link, or this one: \|~~{{#widget:Iframe~~		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}}
	~~\|url=~~http://bugs.sugarlabs.org
	\|~~width=~~900
	\|~~height=~~600
	\|~~border=~~1
	}}}}
	{\| width="100%"		{\| 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:		\|When you visit [http://bugs.sugarlabs.org bugs.sugarlabs.org], you'll see a webpage with this menu in the top right corner:

FGrose at 04:24, 14 April 2010

2010-04-14T04:24:07Z

← Older revision		Revision as of 00:24, 14 April 2010
Line 10:		Line 10:
	=== Log into Trac ===		=== Log into Trac ===

	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 http://bugs.sugarlabs.org - go ahead and click that link.		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 {{Show\|http://bugs.sugarlabs.org - go ahead and click that link, or this one: \|{{#widget:Iframe
			\|url=http://bugs.sugarlabs.org
			\|width=900
			\|height=600
			\|border=1
			}}}}
	{\| width="100%"		{\| 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:		\|When you visit [http://bugs.sugarlabs.org bugs.sugarlabs.org], you'll see a webpage with this menu in the top right corner:

FGrose: q

2010-04-01T18:47:25Z

← Older revision		Revision as of 14:47, 1 April 2010
Line 67:		Line 67:
	* Embed links to mailing list posts, blogs, videos, or other descriptions of the issue or problem, if appropriate.		* Embed links to mailing list posts, blogs, videos, or other descriptions of the issue or problem, if appropriate.
	* Please, please, please cross-reference with links to related tickets, perhaps in http://dev.laptop.org.		* Please, please, please cross-reference with links to related tickets, perhaps in http://dev.laptop.org.
			==== Attach files ====
			* Check the 'I have files to attach to this ticket' box or, on an existing ticket, the [Attach file] button.
			* See [[BugSquad/Get Logs]] for how to review and attach log files.
			* Sometimes screen shots of a problem will help explain it. Pressing <Alt> + 1 in Sugar captures the screen and stores a screen shot in the Journal.
	=== Categorize the ticket ===		=== Categorize the ticket ===

FGrose: moved Talk:Sugar on a Stick/Getting Involved to BugSquad/Bug Report: move to a main page

2010-04-01T15:14:21Z

moved Talk:Sugar on a Stick/Getting Involved to BugSquad/Bug Report: move to a main page

← Older revision	Revision as of 11:14, 1 April 2010
(No difference)