TEXT   13

pro tips

Guest on 6th July 2022 08:48:17 AM

  1. Pro Tips
  2. ********
  3.  
  4. This section distills some Bugzilla tips and best practices that have
  5. been developed.
  6.  
  7.  
  8. Autolinkification
  9. =================
  10.  
  11. Bugzilla comments are plain text - so typing <U> will produce less-
  12. than, U, greater-than rather than underlined text. However, Bugzilla
  13. will automatically make hyperlinks out of certain sorts of text in
  14. comments. For example, the text "http://www.bugzilla.org" will be
  15. turned into a link: http://www.bugzilla.org. Other strings which get
  16. linkified in the obvious manner are:
  17.  
  18. * bug 12345
  19.  
  20. * bugs 123, 456, 789
  21.  
  22. * comment 7
  23.  
  24. * comments 1, 2, 3, 4
  25.  
  26. * bug 23456, comment 53
  27.  
  28. * attachment 4321
  29.  
  30. * mailto:george@example.com
  31.  
  32. * george@example.com
  33.  
  34. * ftp://ftp.mozilla.org
  35.  
  36. * Most other sorts of URL
  37.  
  38. A corollary here is that if you type a bug number in a comment, you
  39. should put the word "bug" before it, so it gets autolinkified for the
  40. convenience of others.
  41.  
  42.  
  43. Comments
  44. ========
  45.  
  46. If you are changing the fields on a bug, only comment if either you
  47. have something pertinent to say or Bugzilla requires it. Otherwise,
  48. you may spam people unnecessarily with bugmail. To take an example: a
  49. user can set up their account to filter out messages where someone
  50. just adds themselves to the CC field of a bug (which happens a lot).
  51. If you come along, add yourself to the CC field, and add a comment
  52. saying "Adding self to CC", then that person gets a pointless piece of
  53. mail they would otherwise have avoided.
  54.  
  55. Don't use sigs in comments. Signing your name ("Bill") is acceptable,
  56. if you do it out of habit, but full mail/news-style four line ASCII
  57. art creations are not.
  58.  
  59. If you feel a bug you filed was incorrectly marked as a DUPLICATE of
  60. another, please question it in your bug, not the bug it was duped to.
  61. Feel free to CC the person who duped it if they are not already CCed.
  62.  
  63. ======================================================================
  64.  
  65. This documentation undoubtedly has bugs; if you find some, please file
  66. them here.

Raw Paste


Login or Register to edit or fork this paste. It's free.