hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-11-24 13:32:42 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

Added metadata.

Browse source
This commit is contained in:
Peter Boy 2023-08-29 12:01:31 +02:00
parent 49df73d37a
commit 696d1bbe78
6 changed files with 73 additions and 64 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
modules/ROOT/pages/bugzilla/correct-component.adoc
View file

@ -1,4 +1,11 @@
= Finding the correct component
= Bugzilla – Finding the Correct Component
Ben Cotton
:revnumber: F36 onwards
:revdate: 2022-03-03
:category: Troubleshooting
:tags: How-to, Bugzilla
//:page-aliases: bugzilla/correct-component.adoc
When filing a bug, it helps if you can identify the component at fault.
This is not always obvious, so here are some tips.

7
modules/ROOT/pages/bugzilla/email-notifications.adoc
View file

@ -1,4 +1,11 @@
= Managing Bugzilla email notifications
Ben Cotton
:revnumber: F36 onwards
:revdate: 2022-03-11
:category: Troubleshooting
:tags: How-to, Bugzilla
//:page-aliases: bugzilla/email-notifications.adoc
Bugzilla allows you to set granular email notification preferences.

18
modules/ROOT/pages/bugzilla/find-duplicates.adoc
View file

@ -1,20 +1,24 @@
= Finding duplicates in Bugzilla
include::partial$attributes.adoc[]
Ben Cotton
:revnumber: F36 onwards
:revdate: 2022-03-03
:category: Troubleshooting
:tags: How-to, Bugzilla
//:page-aliases: bugzilla/find-dublicates.adoc
Fedora developers want to hear about specific and reproducible bugs that happen when you use Fedora Linux, but it does not help to have the same bug reported many times.
You can help to get more bugs fixed faster by checking duplicate reports before filing a new bug.
// include::partial$attributes.adoc[]
Fedora developers want to hear about specific and reproducible bugs that happen when you use Fedora Linux, but it does not help to have the same bug reported many times. You can help to get more bugs fixed faster by checking duplicate reports before filing a new bug.
Commonly encountered bugs can be found:
* On the https://bugzilla.redhat.com/duplicates.cgi?sortby=count&reverse=1&product=Fedora&maxrows=100&changedsince=7[most frequently reported bugs] list
* On the https://fedoraproject.org/wiki/Bugs/Common[Common Bugs] page
For Rawhide bugs, linked from a https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers[Blocker or Target Tracker]
* On the https://fedoraproject.org/wiki/Bugs/Common[Common Bugs] page for Rawhide bugs, linked from a https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers[Blocker or Target Tracker]
If your bug isn't in the lists above, you can use xref:bugzilla/query.adoc[Bugzilla's search tool] to find matching bugs.
== What to do with duplicates once found
If you are a triager or package maintainer, set the bug that has less information to the CLOSED status with a resolution of DUPLICATE, and add the bug number of the bug with the best information.
This may very well mean closing a lower-numbered bug and keeping a higher-numbered one open—that's fine.
If you are a triager or package maintainer, set the bug that has less information to the CLOSED status with a resolution of DUPLICATE, and add the bug number of the bug with the best information. This may very well mean closing a lower-numbered bug and keeping a higher-numbered one open—that's fine.
If you do not have permissions to change bugs you have not reported, add a comment to both bugs pointing out the duplication and someone else will mark them appropriately.

42
modules/ROOT/pages/bugzilla/index.adoc
View file

@ -1,40 +1,33 @@
= Using Bugzilla
Ben Cotton
:revnumber: F36 onwards
:revdate: 2022-03-11
:category: Troubleshooting
:tags: How-to, Bugzilla
//:page-aliases: bugzilla/index.adoc
Fedora uses https://bugzilla.redhat.com[Red Hat Bugzilla] for bug tracking. This page and the other pages under the "Bugs" header on the left offer some tips and guidance.
Fedora uses https://bugzilla.redhat.com[Red Hat Bugzilla] for bug tracking.
This page
and the other pages under the "Bugs" header on the left
offer some tips and guidance.
== Permissions
Any user,
including "anonymous"
(i.e. not logged in)
users can view bugs.
(Note that some bugs or comments may be marked "private"
or restricted to specific groups.
This is rare in Fedora
and is generally to protect sensitive information
that might be in an attachment or log snippet.)
Any user, including "anonymous" (i.e. not logged in) users can view bugs. (Note that some bugs or comments may be marked "private"
or restricted to specific groups. This is rare in Fedora and is generally to protect sensitive information that might be in an attachment or log snippet.)
Any logged-in user can create a bug report
or add a comment to an existing bug.
Any logged-in user can create a bug report or add a comment to an existing bug.
The reporter or assignee of a bug can modify any field in their own bug.
== Automatic changes
Bugzilla will automatically create links to bug reports or comments that follow the pattern
"bug xxxx" or "comment xxxx".
Bugzilla will automatically create links to bug reports or comments that follow the pattern "bug xxxx" or "comment xxxx".
Bugs marked as xref:bugzilla/find-duplicates.adoc[duplicate] will automatically get a comment referring to the other bug report.
The other bug report will automatically get a comment indicating that another bug has been marked as a duplicate of it.
Bugs marked as xref:bugzilla/find-duplicates.adoc[duplicate] will automatically get a comment referring to the other bug report. The other bug report will automatically get a comment indicating that another bug has been marked as a duplicate of it.
https://bodhi.fedoraproject.org[Bodhi] — the Fedora updates system — will automatically comment and change the xref:#_status[status] of associated bugs as updates move through the system.
https://bodhi.fedoraproject.org[Bodhi] —
the Fedora updates system —
will automatically comment
and change the xref:#_status[status]
of associated bugs as updates move through the system.
== Status and resolution
@ -46,6 +39,7 @@ The table below summarizes the statuses.
include::program_management::partial$bz_status.adoc[]
=== Resolution
The table below describes the resolutions that can apply to the _CLOSED_ status.

33
modules/ROOT/pages/bugzilla/query.adoc
View file

@ -1,33 +1,30 @@
= Bugzilla queries
Ben Cotton
:revnumber: F36 onwards
:revdate: 2022-03-04
:category: Troubleshooting
:tags: How-to, Bugzilla
//:page-aliases: bugzilla/find-dublicates.adoc
Bugzilla lets you search for bug reports that match specified conditions. This page covers common options. The https://bugzilla.redhat.com/docs/en/html/using/index.html[Red Hat Bugzilla User Guide] has more information.
Bugzilla lets you search for bug reports that match specified conditions.
This page covers common options.
The https://bugzilla.redhat.com/docs/en/html/using/index.html[Red Hat Bugzilla User Guide] has more information.
== Simple queries
The https://bugzilla.redhat.com/query.cgi?format=specific[simple Bugzilla query form] does a relatively simple keyword search.
Enter a word or short phrase that identifies the problem you saw as uniquely as possible in the Summary field.
Examples: "view source", "auto proxy", "drag drop", "png image".
Enter a word or short phrase that identifies the problem you saw as uniquely as possible in the Summary field. Examples: "view source", "auto proxy", "drag drop", "png image".
== Advanced queries
The https://bugzilla.redhat.com/query.cgi?format=advanced[advanced Bugzilla query form] looks dauntingly complex.
While it is complex and powerful, you can safely ignore most of the form.
Any part of the form that is left blank does not limit the search.
Each part that is filled in cuts the list of bugs down to only those that match the criteria you set.
The https://bugzilla.redhat.com/query.cgi?format=advanced[advanced Bugzilla query form] looks dauntingly complex. While it is complex and powerful, you can safely ignore most of the form. Any part of the form that is left blank does not limit the search. Each part that is filled in cuts the list of bugs down to only those that match the criteria you set.
The Status field is set by default to find NEW, ASSIGNED, NEEDINFO, and MODIFIED bugs—the unfixed bugs (or in the case of MODIFIED the recently fixed bugs).
In the product field, you should always use "Fedora", "Fedora EPEL", or "Fedora Container Images".
In the component field, select the source package that contains the defect.
See the xref:bugzilla/correct-component.adoc[finding the correct component] for help.
In the product field, you should always use "Fedora", "Fedora EPEL", or "Fedora Container Images". In the component field, select the source package that contains the defect. See the xref:bugzilla/correct-component.adoc[finding the correct component] for help.
Enter a word or short phrase that identifies the problem you saw as uniquely as possible in the Summary field.
Examples: "view source", "auto proxy", "drag drop", "png image".
If you enter more than one word and they are not a phrase, change the type of matching for the Summary field from *contains the string* to *contains all of the words/strings* or *contains any of the words/strings*, as appropriate.
Enter a word or short phrase that identifies the problem you saw as uniquely as possible in the Summary field. Examples: "view source", "auto proxy", "drag drop", "png image". If you enter more than one word and they are not a phrase, change the type of matching for the Summary field from *contains the string* to *contains all of the words/strings* or *contains any of the words/strings*, as appropriate.
Fedora generally doesn't make use of keywords in Bugzilla, so you won't usually need to use this.
Keywords are specific tags, not arbitrary words.
If you try to search for keywords that are not on the list, it won't work.
Fedora generally doesn't make use of keywords in Bugzilla, so you won't usually need to use this. Keywords are specific tags, not arbitrary words. If you try to search for keywords that are not on the list, it won't work.

28
modules/ROOT/pages/bugzilla/spam.adoc
View file

@ -1,27 +1,27 @@
= Reporting Bugzilla spam
Ben Cotton
:revnumber: F36 onwards
:revdate: 2022-03-11
:category: Troubleshooting
:tags: How-to, Bugzilla
//:page-aliases: bugzilla/find-dublicates.adoc
Like any website that allows user contribution,
Red Hat Bugzilla sometimes gets spam comments.
There are two ways to report spam.
TIP: If you have the necessary privileges,
you can mark a spam comment as private
until the admins have had a chance to remove it.
Like any website that allows user contribution, Red Hat Bugzilla sometimes gets spam comments. There are two ways to report spam.
TIP: If you have the necessary privileges, you can mark a spam comment as private until the admins have had a chance to remove it.
== Tag comment
The preferred way is to tag the comment as spam.
. On the spam comment,
click the tag icon.
(The alt text says "tag comment".)
. In the text box that opens,
type "spam" and hit the Enter key.
. On the spam comment, click the tag icon. (The alt text says "tag comment".)
. In the text box that opens, type "spam" and hit the Enter key.
This will flag the comment to the Bugzilla admins.
== Report by email
You can submit reports via email to
mailto:bugzilla-owner@redhat.com[bugzilla-owner@redhat.com].
Please include a direct link to the comment(s) you are reporting for spam.
You can submit reports via email to mailto:bugzilla-owner@redhat.com[bugzilla-owner@redhat.com]. Please include a direct link to the comment(s) you are reporting for spam.