Setting up for the new year

[amedyne]

Your help has been critical to getting Firefox for Android (aka Fenix) this far, and it’s been amazing and continues to grow. We thank you for your contribution, suggestions and feedback to get to where we are now. We are excited about recent enhancements that have been added to Firefox for Android and we want the momentum to continue.
To help us keep growing, and to make sure your input gets seen and stays effective, we're going to be cleaning up the issue database for Fenix. The volume of issues, combined with having limited time to review and tag them properly, has created a situation where there are currently more than 2000+ open tickets. Most of these issues have been inactive for several months and they reference versions of Fenix that are no longer available.

### A new beginning

To get the Fenix project to a point where we can act quickly on timely feedback from the community, we need to get out from under this backlog so that we can effectively address our current issues in the Github repository and deliver the features our community is asking for. Community involvement plays a large role in our development and planning process, and we closely follow the forums and other feedback channels.

We are taking the following steps in order to turn this repository into an up-to-date, functional issue tracker for bug reports:

1. The issue templates have been updated as a guide on what information you need to provide when submitting tickets in GitHub:

• 🐞 Bug report: Create a report to help us improve
• ⭐️ Feature request: Suggest an idea for this project
• 💻 Web content issue report: Create an issue specifically about something wrong with web content while using Fenix
• ⛏ Investigative Spike: Create an investigation spike
• 📈 Telemetry User Story: Create a telemetry user story, assigned to an Epic to track telemetry
• 💔 Intermittent UI Test Issue: Create an issue to help log a UI test failure
• 👩🏻‍💻 User Story: Create a user story for an epic

2. Issues that have no activity or updates after August 30, 2020 will be closed by an automated process as part of this cleanup effort.

### Out with the old, in with the new and improved

Users are welcome to re-submit bug reports that follow the updated issue template and that still affect the current release of Firefox for Android (aka Fenix). By re-submitting valid issues with up-to-date reproduction steps, the developers will be better equipped to solve any underlying problems. Please include the legacy issue ID in your new submission if there is important context available in the old thread.

We need the community to help us with this step, and we sincerely appreciate your participation in this cleanup effort.
We believe that these actions will improve the development cycle and make the process easier to follow for everyone involved. We apologize in advance for the flood of email notifications, but the pain is temporary and a brighter future awaits.

┆Issue is synchronized with this Jira Task

[cadeyrn]

@amedyne

Thanks for the effort to cleaning up the issues tracker.

The issue templates have been updated as a guide on what information you need to provide when submitting tickets in GitHub

Maybe it's the perfect time to address #14607 as an improvement to the bug template. What do you think?

[hwinnemoe]

Issues that have no activity or updates after August 30, 2020 will be closed by an automated process as part of this cleanup effort.

Will this also include feature requests? If that is the case, there are still some valid feature requests that would be affected by this, e.g. see the feature requests mentioned in #13302.