TEXT   23

editing txt

Guest on 22nd July 2022 01:52:26 AM

  1. Editing a Bug
  2. *************
  3.  
  4.  
  5. Attachments
  6. ===========
  7.  
  8. Attachments are used to attach relevant files to bugs - patches,
  9. screenshots, test cases, debugging aids or logs, or anything else
  10. binary or too large to fit into a comment.
  11.  
  12. You should use attachments, rather than comments, for large chunks of
  13. plain text data, such as trace, debugging output files, or log files.
  14. That way, it doesn't bloat the bug for everyone who wants to read it,
  15. and cause people to receive large, useless mails.
  16.  
  17. You should make sure to trim screenshots. There's no need to show the
  18. whole screen if you are pointing out a single-pixel problem.
  19.  
  20. Bugzilla stores and uses a Content-Type for each attachment (e.g.
  21. text/html). To download an attachment as a different Content-Type
  22. (e.g. application/xhtml+xml), you can override this using a
  23. 'content_type' parameter on the URL, e.g. "&content_type=text/plain".
  24.  
  25. Also, you can enter the URL pointing to the attachment instead of
  26. uploading the attachment itself. For example, this is useful if you
  27. want to point to an external application, a website or a very large
  28. file.
  29.  
  30. It's also possible to create an attachment by pasting text directly in
  31. a text field; Bugzilla will convert it into an attachment. This is
  32. pretty useful when you are copying and pasting, to avoid the extra
  33. step of saving the text in a temporary file.
  34.  
  35.  
  36. Flags
  37. =====
  38.  
  39. To set a flag, select either + or - from the drop-down menu next to
  40. the name of the flag in the Flags list. The meaning of these values
  41. are flag-specific and thus cannot be described in this documentation,
  42. but by way of example, setting a flag named review + may indicate that
  43. the bug/attachment has passed review, while setting it to - may
  44. indicate that the bug/attachment has failed review.
  45.  
  46. To unset a flag, click its drop-down menu and select the blank value.
  47. Note that marking an attachment as obsolete automatically cancels all
  48. pending requests for the attachment.
  49.  
  50. If your administrator has enabled requests for a flag, request a flag
  51. by selecting ? from the drop-down menu and then entering the username
  52. of the user you want to set the flag in the text field next to the
  53. menu.
  54.  
  55.  
  56. Time Tracking
  57. =============
  58.  
  59. Users who belong to the group specified by the "timetrackinggroup"
  60. parameter have access to time-related fields. Developers can see
  61. deadlines and estimated times to fix bugs, and can provide time spent
  62. on these bugs. Users who do not belong to this group can only see the
  63. deadline but not edit it. Other time-related fields remain invisible
  64. to them.
  65.  
  66. At any time, a summary of the time spent by developers on bugs is
  67. accessible either from bug lists when clicking the "Time Summary"
  68. button or from individual bugs when clicking the "Summarize time" link
  69. in the time tracking table. The "summarize_time.cgi" page lets you
  70. view this information either per developer or per bug and can be split
  71. on a month basis to have greater details on how time is spent by
  72. developers.
  73.  
  74. As soon as a bug is marked as RESOLVED, the remaining time expected to
  75. fix the bug is set to zero. This lets QA people set it again for their
  76. own usage, and it will be set to zero again when the bug is marked as
  77. VERIFIED.
  78.  
  79.  
  80. Life Cycle of a Bug
  81. ===================
  82.  
  83. The life cycle of a bug, also known as workflow, is customizable to
  84. match the needs of your organization (see Workflow). The image below
  85. contains a graphical representation of the default workflow using the
  86. default bug statuses. If you wish to customize this image for your
  87. site, the diagram file is available in Dia's native XML format.
  88.  
  89. [image]
  90.  
  91. ======================================================================
  92.  
  93. This documentation undoubtedly has bugs; if you find some, please file
  94. them here.

Raw Paste


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