Will create a new global custom field called "Workaround" - dkl - Normally done in the closing comments. - max - Having a workaround field allow you to quickly see if there is a workaround quickly without reading pages of comments. - kab - Stats: how often is this field used? - Would adding it to bugzilla be jboss specific or generally useful to all products? How would it impact therelease notes for example? Competitor? overlaps? - dkl - TIME ESTIMATE: Add custom field for recording workaround description: 5 hours
*** Bug 714953 has been marked as a duplicate of this bug. ***
A few comments: Echoing and adding to Max's comment in the description, having the field means one can find a workaround or see if there is one, and allows reporting on whether there are workarounds. From a quick search on jira, for the JBPAPP project I see 4.6% of cases had a workaround indicated (288/6236) Having a workaround field means we don't have to rely on communicated/error prone conventions such as "repeat or add in the closing comment." The field is intuitively clear. Finally, using comments means that the workaround cannot be edited. If there is a problem, or a better workaround, etc., it means the workaround has to be repeated/updated in a new comment making searching for workaround information more cumbersome.
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
As noted previously, the Bugzilla Team is cleaning up a large number of outstanding issues that have bit rotted. This bug is being closed as there has been no response to that notification. If you believe this bug is still important please reopen this bug in the NEW status and PM will consider it.