[fenix] For https://github.com/mozilla-mobile/fenix/issues/26855 - Direct users to Bugzilla for issue tracking
Gabriel Luong
1 year ago
committed by
Christian Sadilek
parent
549cfb2974
commit
24cc414d67
@ -1,91 +0,0 @@
|
||||
name: "\U0001F41E Bug report"
|
||||
description: Create a report to help us improve.
|
||||
title: "[Bug]: "
|
||||
labels: ["\U0001F41E bug", "needs:triage"]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
- Please do your best to search for duplicate issues before filing a new issue so we can keep our issue board clean.
|
||||
- Have a look at ["I want to file an issue!"][info] for more information.
|
||||
- Read the [Community Participation Guidelines][guidelines] and the [Bugzilla Etiquette guidelines][bugzilla] before filing an issue.
|
||||
|
||||
[info]: https://github.com/mozilla-mobile/fenix#i-want-to-file-an-issue
|
||||
[guidelines]: https://www.mozilla.org/en-US/about/governance/policies/participation/
|
||||
[bugzilla]: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Steps to reproduce
|
||||
description: Steps to reproduce the behaviour.
|
||||
placeholder: |
|
||||
1. Have a tab open..
|
||||
2. Go to..
|
||||
3. Click on..
|
||||
4. Observe..
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Expected behaviour
|
||||
placeholder: A menu should open..
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Actual behaviour
|
||||
placeholder: The app closes unexpectedly..
|
||||
validations:
|
||||
required: true
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
# Device information
|
||||
- type: input
|
||||
attributes:
|
||||
label: Device name
|
||||
description: The name of the device model and manufacturer.
|
||||
placeholder: Google Pixel 2
|
||||
validations:
|
||||
required: false
|
||||
- type: input
|
||||
attributes:
|
||||
label: Android version
|
||||
description: You can find the Android version information in the About section of your device's system settings.
|
||||
placeholder: Android 10
|
||||
validations:
|
||||
required: true
|
||||
- type: dropdown
|
||||
attributes:
|
||||
label: Firefox release type
|
||||
description: You can find this information in Settings -> About Firefox.
|
||||
options:
|
||||
- Firefox Nightly
|
||||
- Firefox Beta
|
||||
- Firefox
|
||||
validations:
|
||||
required: true
|
||||
- type: input
|
||||
attributes:
|
||||
label: Firefox version
|
||||
description: You can find this information in Settings -> About Firefox.
|
||||
placeholder: 89.0.10
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Device logs
|
||||
description: |
|
||||
Device logs or crash information can greatly aid in debugging. You can find some details here on how to [retrieve device logs or crash IDs][log].
|
||||
|
||||
[log]: https://github.com/mozilla-mobile/fenix/wiki/Logging-Crash-Information
|
||||
validations:
|
||||
required: false
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Additional information
|
||||
description: |
|
||||
If you have any additional information for us, use the field below.
|
||||
Please note, you can attach screenshots or screen recordings here, by
|
||||
dragging and dropping files in the field below.
|
||||
validations:
|
||||
required: false
|
||||
@ -1,19 +0,0 @@
|
||||
---
|
||||
name: "⌛ Performance issue"
|
||||
about: Create a performance issue if the app is slow or it uses too much memory, disk space, battery, or network data
|
||||
title: ""
|
||||
labels: "performance"
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Steps to reproduce
|
||||
|
||||
### Expected behavior
|
||||
|
||||
### Actual behavior
|
||||
|
||||
### Device information
|
||||
|
||||
* Android device: ?
|
||||
* Fenix version: ?
|
||||
@ -1,25 +0,0 @@
|
||||
---
|
||||
name: "\U0001F4BB Web content issue report"
|
||||
about: Create an issue specifically about something wrong with web content while using Fenix
|
||||
title: "[webcontent]"
|
||||
labels: "\U0001F4BB bug"
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Site with issue and any steps to reproduce
|
||||
|
||||
### Expected behavior
|
||||
|
||||
### Actual behavior
|
||||
|
||||
### Does toggling Tracking Protection fix the issue? (Press the shield icon in the toolbar while on the site to see toggle)
|
||||
|
||||
### Can you reproduce in Chrome (or other non-Mozilla browser)?
|
||||
<!--- Note: If you can reproduce the same issue in Firefox for Android AND Chrome, this issue is very unlikely to be fixed by our teams. -->
|
||||
<!-- If you cannot reproduce in Chrome and know how to do so, please consider filing a Bugzilla issue here for faster triage https://bugzilla.mozilla.org/enter_bug.cgi?product=GeckoView&component=General -->
|
||||
|
||||
### Device information
|
||||
|
||||
* Android device: ?
|
||||
* Fenix version: ?
|
||||
@ -1,24 +0,0 @@
|
||||
---
|
||||
name: "\U000026CF Investigative Spike"
|
||||
about: Create an investigation spike
|
||||
title: "[Spike]"
|
||||
|
||||
---
|
||||
|
||||
## Title
|
||||
Brief description of what needs to be investigated, including the User story for which the spike is needed.
|
||||
|
||||
## Description
|
||||
Description of what is being investigated, including:
|
||||
Method of investigation (engineering research, prototype, etc.
|
||||
Boundaries of investigation (time box to x hours, does not include UX, etc.)
|
||||
|
||||
## Deliverables
|
||||
Description of deliverables, including:
|
||||
Documentation of investigation results (within the spike ticket, or linked to it), including:
|
||||
Findings
|
||||
Recommendations
|
||||
List of possible user stories to implement recommendations, including estimates
|
||||
Next Steps
|
||||
Reach out to Product to go over results of investigation.
|
||||
|
||||
@ -1,21 +0,0 @@
|
||||
---
|
||||
name: "\U0001F4C8 Telemetry User Story"
|
||||
about: Create a telemetry user story, assigned to an Epic to track telemetry
|
||||
title: "[Telemetry]"
|
||||
labels: Feature:Telemetry
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Description & Product Manager / Data Scientist User Story
|
||||
|
||||
## What questions will you answer with this data?
|
||||
|
||||
## Acceptance Criteria
|
||||
- [ ] ENG files a [DS JIRA](https://jira.mozilla.com/projects/DO/issues/DO-228?filter=allopenissues) request outlining their methodology.
|
||||
- [ ] DS sign off on instrumentation methodology addressing product questions.
|
||||
- [ ] Event pings can be queried via re:dash
|
||||
- [ ] Event pings can be queried via amplitude
|
||||
- [ ] We are sending telemetry events for the actions listed in the requirements
|
||||
- [ ] We have documented the telemetry
|
||||
- [ ] We have asked a data steward to [review](https://github.com/mozilla/data-review/blob/master/request.md) the telemetry
|
||||
@ -1,13 +0,0 @@
|
||||
---
|
||||
name: "\U0001F494 Intermittent UI Test Issue"
|
||||
about: Create an issue to help log a UI test failure
|
||||
labels: "eng:ui-test, intermittent-test"
|
||||
title: "Intermittent UI test failure - <Classname.testName>"
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Firebase Test Run:
|
||||
Provide a Firebase test run report link here showcasing the problem
|
||||
### Stacktrace:
|
||||
### Build:
|
||||
@ -1,13 +0,0 @@
|
||||
---
|
||||
name: "\U0001F6A8 Intermittent Unit Test Issue"
|
||||
about: Create an issue to help log a Unit Test failure
|
||||
labels: "eng:intermittent-test"
|
||||
title: "Intermittent Unit Test failure - <Classname.testName>"
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
### Test Run:
|
||||
Provide a test run report link here showcasing the problem (e.g, Taskcluster), and a link to the source Github event
|
||||
### Stacktrace:
|
||||
### Build:
|
||||
@ -0,0 +1,5 @@
|
||||
blank_issues_enabled: false
|
||||
contact_links:
|
||||
- name: We are now using Bugzilla for issue tracking!
|
||||
url: https://bugzilla.mozilla.org/enter_bug.cgi?product=Fenix
|
||||
about: Please file your ticket there, and select the corresponding component from the list. If the component is not in the list, select "General". In commit messages, please reference the ticket using "Bug 1234567 - " as prefix.
|
||||
Loading…
Reference in New Issue