0003152: Adding notes and documents to resolved bugs - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0003152	mantisbt	bugtracker	public	2003-04-23 00:04	2004-07-08 07:09

Reporter	ndeboer	Assigned To	vboctor
Priority	normal	Severity	feature	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	0.18.0a4
Fixed in Version	0.19.0a1

Summary	0003152: Adding notes and documents to resolved bugs
Description	When it is possible to add notes and documents to resolved bugs, clients (reporters) could comment on the resolution. Then developers could close of reopen a bug. Now clients (reporters) must communicate with other means (phone or e-mail), so this is not recorded in the bugtracking system.
Tags	No tags attached.

vboctor 2003-04-23 00:15 manager ~0004236	This can be achieved through the following configuration option: Bug is resolved, ready to be closed or reopened. In some custom installations a bug maybe considered as resolved when it is moved to a custom (FIXED OR TESTED) status. $g_bug_resolved_status_threshold = RESOLVED; Let me know if this achieves what you need.

ndeboer 2003-04-23 00:29 reporter ~0004237	Yes, I think it is. Don't know exactly how to create a custom status yet, though. I should have read the ChangeLog file. Sorry.

vboctor 2003-04-23 01:38 manager ~0004239	You don't need to create custom status, what you can do is to set the resolved status to CLOSED. Which should cause the bug to become read-only when closed rather than when RESOLVED.

ndeboer 2003-04-23 09:36 reporter ~0004245	Yes, but then you also get the 'Resolve bug' button even when it is allready resolved. This might be a bit confusing. It is workable though.

vboctor 2004-05-17 07:52 manager ~0005521	The following was implemented and committed to CVS. This will be included in 0.19.0. New Config: bug_readonly_status_threshold (default RESOLVED). Status threshold after which the issue is considered readonly. New Config: update_readonly_bug_threshold (default MANAGER). Status threshold after which the user is allowed to edit readonly issues. bug_resolved_status_threshold is now used rather than the hard-coded RESOLVED status when a bug is resolved. The above options should give enough flexibility to achieve what you need.