Projeto no Phabricator: [[phab:tag/{{{phabricator}}}/|#{{{phabricator}}}]]
Jdm/webtools-bmo-bugzilla forked from mozilla-bteam/bmo. For example, if you want to override some CSS in skins/standard/global.css, then you should. Created attachment 211923 docs patch for tip v2 only for tip, for others should not include + para> + As of Bugzilla 2.22, individual bugs can be saved and added + to a Saved Search. + para> Attachment #207895 - Attachment is obsolete: true.
This page is a translated version of the page Template:Skin and the translation is 0% complete.
English • dansk • français • magyar • polski • português do Brasil • 中文 • 日本語
This template should be added to all skin pages on this wiki (but only the main page) to display an information box and categorize the skin.
- 5Using the infobox
- 6Enhancing this template
Usage
Copy and paste: For help with parameter values, see below. |
|
Content parameters
This section describes parameters that govern infobox content. For help with templatemode and other control parameters, please see Control parameters.
Parameter | Description |
---|---|
name | name of the skin |
status | current release status One of:
If the status is anything other than the above, it will be ignored and the default value of 'Unknown' will be displayed in the template instead. |
username | The author's username on MediaWiki.org (if they have one). May be omitted, but if present it will be used to link to the author's user & user_talk page. It should be provided without namespace and without [[]]s. |
author | The skin author's name, if different from their MediaWiki.org username. Free text. If omitted then the 'username' field will be used (if present). |
description | short description |
image | screenshot or logo of skin. It should be provided without namespace and without [[]]s. |
imagesize | facultative, size of the image (default size is 220px) |
version | last version |
update | date of the last update |
mediawiki | required version of MediaWiki |
php | required version of PHP |
license | license(s) governing use of this skin, e.g. GPL |
download | link to the download : If you put the code into page in the MediaWiki wiki, link to it using a full page name and section name, e.g. [[Skin:Example/version_1.22a#Code]] (it must remain valid when bot-copied elsewhere) |
readme | external link to the readme file |
changelog | external link to the changelog file |
parameters | available parameters for LocalSettings.php |
example | example, website or screenshot of working skin |
compatibility | compatibility chart, e.g. Template:Extension Testing |
bugzilla | Bugzilla MediaWiki skin component name |
Control parameters
Parameter | Description |
---|---|
templatemode | Controls auto-categorization of host page. Normally left blank. Alternate values are:
If this is left blank, this template will add the host page to Category:All skins and to one or more additional categories, depending on the values assigned to the Content parameters. |
Categories added
This template will automatically add the pages it is used on to the Category:All skins category.
In addition, it will categorize the page based on the value of the status parameter:
- unstable: Category:Unstable skins
- experimental: Category:Experimental skins
- stable: Category:Stable skins
- beta: Category:Beta status skins
- unmaintained: Category:Unmaintained skins
- otherwise: Category:Skins with unknown status
Using the infobox
Existing skin pages
If you want to add the infobox to an existing page, copy and paste the code at the top of this page.
Create a new skin article
If you want to create a new skin page, enter the name below and click the button. A new page will be created with the infobox template already in place.
Please replace 'TheSkin' with your skin's name:
MediaWiki is an open-source project and users are encouraged to make any MediaWiki skins under an Open Source Initiative (OSI) approved GPLv2 compatible license (including MIT, BSD, PD). For skins that have a compatible license, you can request commit access to the MediaWiki source repository for skins.
A developer sharing their code in the code repository should expect:
- Feedback / Criticism / Code reviews
- Review and comments by other developers on things like framework use, security, efficiency and usability.
- Developer tweaking
- Other developers modifying your submission to improve or clean-up your code to meet new framework classes and methods, coding conventions and translations.
- Future versions by other developers
- New branches of your code being created by other developers as new versions of MediaWiki are released.
- Credit
- Credit for your work being preserved in future versions
- Similarly, you should credit the developers of any skins whose code you borrow from.
Any developer who is uncomfortable with any of these actions occurring should not host their code in the code repository. You are still encouraged to create a summary page for your skin on the wiki to let people know about the skin, and where to download it.
Enhancing this template
If you would like to improve on this template, thanks! This is a complicated template so here is some help along the way:
In addition, Template:Skin/Sample stores the boiler plate that is preloaded into newly created pages and contains some basic documentation on how to fill in the template parameters. It needs to be kept in sync with Template:Skin/doc.
The Create skin button
To improve the create skin button behavior:
- Template:Skin/Sample: The boilerplate skin that is preloaded into newly-created pages.
- Template:Skin/CreateSkinInputBox: An input box that can be inserted wherever you want users to easily create skins. For documentation on the
<inputbox>
tag, please see Extension:InputBox. - Skin:TheSkin: - Defines a placeholder, in case a user accidentally hits the create button without changing the skin name.
Infobox parameters
In general:
- To make this template easy to use, each label in the infobox is linked to documentation on the template parameter(s) it displays. If you add a parameter, please be sure to also add it to the content parameter documentation and link its label to that documentation.
Test case
See if the following pages are still ok, after edited this template.
A documentação acima foi transcluída de Template:Skin/pt-br/doc. (editar | histórico)
Editores podem experimentar na sandbox (criar | mirror) desta predefinição e páginas de testcases (criar).
Subpáginas desta predefinição.
Editores podem experimentar na sandbox (criar | mirror) desta predefinição e páginas de testcases (criar).
Subpáginas desta predefinição.
Retrieved from 'https://www.mediawiki.org/w/index.php?title=Template:Skin/pt-br&oldid=3442036'
What is Bugzilla?
Bugzilla is an open-source issue/bug tracking system that allows developers to keep track of outstanding problems with their product. It is written in Perl and uses MYSQL database.
Bugzilla is a Defect tracking tool, however, it can be used as a test management tool as such it can be easily linked with other Test Case management tools like Quality Center, Testlink etc.
This open bug-tracker enables users to stay connected with their clients or employees, to communicate about problems effectively throughout the
Step 3) You are successfully logged into Bugzilla system
Creating a Bug-report in Bugzilla
Step 1) To create a new bug in Bugzilla, visit the home-page of Bugzilla and click on NEW tab from the main menu
Step 2) In the next window
- Enter Product
- Enter Component
- Give Component description
- Select version,
- Select severity
- Select Hardware
- Select OS
- Enter Summary
- Enter Description
- Attach Attachment
- Submit
NOTE: The above fields will vary as per your customization of Bugzilla
NOTE: The mandatory fields are marked with *.
In our case field's
- Summary
- Description
Are mandatory
If you do not fill them you will get a screen like below
Step 4) Bug is created ID# 26320 is assigned to our Bug. You can also add additional information to the assigned bug like URL, keywords, whiteboard, tags, etc. This extra-information is helpful to give more detail about the Bug you have created.
- Large text box
- URL
- Whiteboard
- Keywords
- Tags
- Depends on
- Blocks
- Attachments
Step 5) In the same window if you scroll down further. You can select deadline date and also status of the bug. Deadline in Bugzilla usually gives the time-limit to resolve the bug in given time frame.
Create Graphical Reports
Graphical reports are one way to view the current state of the bug database. You can run reports either through an HTML table or graphical line/pie/bar-chart-based one. The idea behind graphical report in Bugzilla is to define a set of bugs using the standard search interface and then choosing some aspect of that set to plot on the horizontal and vertical axes. You can also get a 3-dimensional report by choosing the option of 'Multiple Pages'.
Reports are helpful in many ways, for instance, if you want to know which component has the largest number of bad bugs reported against it. In order to represent that in the graph, you can select severity on X-axis and component on Y-axis, and then click on generate a report. It will generate a report with crucial information.
The graph below shows the Bar chart representation for the Bugs severity in component 'Widget Gears'. In the graph below, the most severe bug or blockers in components are 88 while bugs with normal severity are at the top with 667 number.
Likewise, we will also see the line graph for %complete Vs Deadline
Step 1) To view your report in a graphical presentation,
- Click on Report from Main Menu
- Click on the Graphical reports from the given option
Step 2) Let's create a graph of % Complete Vs Deadline
In here on the vertical axis we chose % Complete and on our horizontal axis we chose Deadline. This will give the graph of amount of work done in percentage against the set-deadline.
Now, set various option to present reports graphically
- Vertical Axis
- Horizontal Axis
- Multiple Images
- Format- Line graph, Bar chart or Pie chart
- Plot data set
- Classify your bug
- Classify your product
- Classify your component
- Classify bug status
- Select resolution
- Click on generate a report
The image of the graph will appear somewhat like this
Browse Function
Step 1) To locate your bug we use browse function, click on Browse button from the main menu.
Step 2) As soon as you click on browse button a window will open saying 'Select a product category to browse' as shown below, we browse the bug according to the category.
- After clicking the browse button
- Select the product 'Sam's Widget' as such you have created a bug inside it
Step 3) It opens another window, in this click on component 'widget gears'. Bugzilla Components are sub-sections of a product. For instance, where our product is SAM'S WIDGET whose component is WIDGET GEARS.
Step 4) when you click on the component, it will open another window. All the Bugs created under particular category will be listed over here. From that Bug-list, choose your Bug#ID to see more details about the bug.
It will open another window, where information about your bug can be seen more in detail. In the same window, you can also change the assignee, QA contact or CC list.
How to use Simple search option in Bugzilla
Bugzilla provides two ways of searching for bugs, they are Simple Search and Advance Search methods.
Step 1) We will first learn the 'Simple Search' method. Click on search button from the main menu and then follow these steps
- Click on 'Simple Search' button
- Choose the status of the Bug – choose Open if you are looking the bug in Open status and closed for bug in closed status
- Choose your category and component, and you can also put keywords related to your bug
- Click on the search
Step 2) Here we will search for both option open and closed status, first we have selected closed status for bug and clicked search button.
For closed status, it fetched 12 bugs.
Step 3) Likewise we have searched for Open status as well, and it has fetched 37 bugs related to our queries.
Also, at the bottom of the screen you have various options like how you want to see your bug - an XML format, in Long format or just Time summary. Apart from that you can also use other option like send mail to bug assignee, change several bugs at once or change column of the screen, etc.
![Bugzilla Bugzilla](http://photos1.blogger.com/blogger/483/738/1600/napkin1.jpg)
In next step, we will demonstrate one of this function change column of the screen, through which we will learn how to add or remove the column to the existing column.
How to add or remove a column to default search screen
Step 1) Click on the Change Column as shown in above screen-shot. It will open a new window where you have to follow these steps.
- Select any given option from the column you want to appear in the main screen - here we have selected % complete
- Click on the arrow button, it will move % complete column from àAvailable Column to the Selected column
These steps will move the selected column from left to right.
The % complete is moved from left to right as shown below, and once we click on change column it will appear in the main screen
Before- Search result screen before using 'Change Column' option-
- There is no % complete column appears in search screen result as shown below
After- Search result screen after using 'Change Column' option
- You can see % complete column added to the extreme right in the existing column in the main screen, which was not their previously.
NOTE: Likewise you can remove or add any column you want.
How to use Advanced Search in Bugzilla
Step 1) After a Simple search we will look into the Advanced Search option for that you have to follow the following steps.
- Click on the advanced search option
- Select option for a summary, how you want to search
- Enter the keyword for your bug- for example, Widget gears twisted
- Select the category of your Bug under classification, here we selected Widget
- Choose your product under which your Bug was created- Sam's Widget
- Component- Widget gears
- Status- Confirmed
- Resolution
Step 2) Once you select all the option, click on search button. It will detect the bug you created
The advanced search will find your bug, and it will appear on the screen like this
How to use preferences in BugZilla
Preferences in Bugzilla is used to customize the default setting made by Bugzilla as per our requirement. There are mainly five preferences available
- General Preferences
- E-mail Preferences
- Saved Searches
- Account Information
- Permissions
General Preferences
For general preferences, you have a various option like changing Bugzilla general appearance, a position of the additional comment box, automatically add me to cc, etc. Here we will see how to change the general appearance of the Bugzilla.
There are many changes you can do which are self-explanatory, and you can choose the option as per your requirement.
Step 1)
- To set the background Skin of Bugzilla
- Go to Bugzilla general preference (Skin)
- Select the option you want to see as a change and submit the change ( DuskàClassic )
- A message will appear on the window saying changes have been saved, as soon as you submit the changes
After the skin preference is changed to Classic from Dusk, the background color of the screen appears white
Likewise, for other default settings changes can be done.
E-mail preferences
E-mail preferences enable you to decide how to receive the message and from whom to receive the messages.
Step 1) To set the e-mail preferences
- Click on e-mail services
- Enable or disable the mail to avoid receiving notification about changes to a bug
- Receiving a mail when someone asks to set a flag or when someone sets a flag you asked for
- When and from whom you want to receive mail and under which condition. After marking your option at the end, submit the changes.
Saved Searches Preference
Saved searches preference gives you the freedom to decide whether to share your bug or not to share.
Step 1) Click on saved searches, it will open window with the option like edit bugs, don't share, can confirm, etc. Choose the option as per your need.
Step 2) We can run our bug from 'Saved Searches'.
- Go to Saved Searches under preference
- Click on the 'Run' button
As soon as you run your search from Saved Searches it opens your bug as shown below
Step 3) In the same window we can also choose specific users with whom we want to share the search by marking or unmarking the checkbox against the users
That's all to BugZilla!