BugZilla

Chooi-Mey wrote:

Based on the feedback from the team, below 5 items have been raised:

1. Deployment date - Add a field for the date of deployment to production, to captured the deployment date when the changes/bugs is deployed to LIVE (status change to Deployed).

• Added custom field Deployment Date in bug creation and change.

1. File attachment storage - File attachment to be stored in file system structure by YEAR layer basis, to avoid over grow of the folder limit in OS level.

• Added year layer base on the bug creation year.

1. Attachment deletion permission - refer to http://devzing.com/blog/index.php/bugzilla-tip-deleting-attachment

The attachment deletion is only allowed for Administrator (if the setting is turn on), while for non-administrator, it can only be set as obsolete.

• No change, since no others config found.

1. Bugs related/Dependency - Current logic when define bug dependency, it will trigger email to alert the bug reporter/related party for the first time, after that, any changes on this bug will not trigger email to the depends bug.

Try find out any features allow to set Bug Related, instead of dependency.

• added custom field Related in bug creation and change. (NOTE : ONLY 1 bug id allowed)

1. Bug Comment Textarea field - find out any text formatting/html content is allowed.

• For security reasons Bugzilla ignores HTML tags in comments (As refer to http://www.bugzilla.org/docs/2.18/html/faq.html#faq-phb-emailapp & http://www.bugzilla.org/docs/4.0/en/html/security-bugzilla.html - Accessed on 1700 15th July 2013)
• As refer to http://www.bugzilla.org/docs/4.0/en/html/hintsandtips.html#id530113 (Accessed on 1700 15th July 2013) , Bugzilla will automatically make hyperlinks out of certain sorts of text in comments, Example as below :

bug 1
comment 2
bug 2, comment 3
attachment 3
http://www.bugzilla.org/
Lines beginning with the ">" character are assumed to be quotes