🗑️Archive best possible bug database Rule

rules/build-the-backlog/rule.md

@@ -11,7 +11,10 @@ authors:
     url: https://ssw.com.au/people/greg-harris
   - title: Matt Goldman
     url: https://ssw.com.au/people/matt-goldman
-related: []
+related:
+- github-issue-templates
+- do-you-have-templates-for-your-pbis-and-bugs
+- turn-emails-into-pbis
 redirects:
   - product-owner-do-you-know-how-to-update-the-backlog
 created: 2010-09-15T15:18:19.000Z

rules/do-you-keep-the-best-possible-bug-database/rule.md

@@ -1,14 +1,15 @@
 ---
 type: rule
-archivedreason: 
+archivedreason: "Bugs are usually tracked using GitHub Issues (or similar) and Team Companion is dead. Superceded by related Rule"
 title: Do you keep the best possible bug database?
 guid: 6159eae3-6e8b-4999-8812-0907c53db7fd
 uri: do-you-keep-the-best-possible-bug-database
 created: 2009-02-28T09:44:02.0000000Z
 authors:
 - title: Adam Cogan
   url: https://ssw.com.au/people/adam-cogan
-related: []
+related:
+- build-the-backlog
 redirects: []
 
 ---
@@ -17,7 +18,7 @@ There are 101 bug databases on the market at the moment and of course many compa
 
 <!--endintro-->
 ![](bugs.jpg)
-This is a common scenario: Your tester/client finds a bug, they log on to your on-line bug database, and enter the data, they save the error message as a gif and upload the image. As Project Manager, you get notified by email of the bug, you log on to the application, view the image, review the status, assign a priority, and assign it to a developer. The developer receives the email, logs on and sets about fixing the bug. When completed, he logs back on to the application, enters a completed date, and an email is sent to the tester/client. The tester/client logs on, and is told what to test, reviews the work, enters a checked by date, and the final email is sent to the manager who closes the bug.
+This is a common scenario: Your tester/client finds a bug, they log on to your on-line bug database, and enter the data, they save the error message as a gif and upload the image. As Project Manager, you get notified by email of the bug, you log on to the application, view the image, review the status, assign a priority, and assign it to a developer. The developer receives the email, logs on and sets about fixing the bug. When completed, they logs back on to the application, enters a completed date, and an email is sent to the tester/client. The tester/client logs on, and is told what to test, reviews the work, enters a checked by date, and the final email is sent to the manager who closes the bug.
 
 Phew! That sounds like a lot of steps which is why most people resort to just sending an email. I believe most people send requests for tasks via email, if this is the case, why should developers have a separate "to-do" list, in the form of a bug-database in which they re-enter data?