View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003946 | mantisbt | bugtracker | public | 2004-06-16 21:07 | 2004-07-07 18:47 |
Reporter | Eric Seppanen | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.18.3 | ||||
Fixed in Version | 0.19.0a1 | ||||
Summary | 0003946: Allow bugnotes on resolved or closed bugs | ||||
Description | I find it very useful to be able to comment on resolved or closed bugs. There's any number of reasons why you might want to add notes even after a bug is fixed, and doing the reopen-comment-close is a pain. Sure, it's probably not for everyone, but maybe some will find it useful. Patch attached. Maybe this would make sense as a config file option? | ||||
Tags | No tags attached. | ||||
Attached Files | bugnote.patch (581 bytes)
--- bugnote_add_inc.php.orig Sun Jan 11 01:16:06 2004 +++ bugnote_add_inc.php Wed Jun 16 20:46:30 2004 @@ -9,8 +9,7 @@ # $Id: bugnote_add_inc.php,v 1.16 2004/01/11 07:16:06 vboctor Exp $ # -------------------------------------------------------- ?> -<?php if ( ( $t_bug->status < config_get( 'bug_resolved_status_threshold' ) ) && - ( access_has_bug_level( config_get( 'add_bugnote_threshold' ), $f_bug_id ) ) ) { ?> +<?php if ( access_has_bug_level( config_get( 'add_bugnote_threshold' ), $f_bug_id ) ) { ?> <?php # Bugnote Add Form BEGIN ?> <br /> <a name="addbugnote"> | ||||
I already implemented this sometime ago in CVS. It will be included in 0.19.0 Bug becomes readonly if its status is >= this status. The bug becomes read/write again if re-opened and itsstatus becomes less than this threshold.$g_bug_readonly_status_threshold = RESOLVED; Threshold needed to update readonly bugs. Readonly bugs are identified via$g_bug_readonly_status_threshold.$g_update_readonly_bug_threshold = MANAGER; |
|