0004648: Assign To independent of $g_update_bug_threshold - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0004648	mantisbt	feature	public	2004-10-01 02:54	2004-11-06 06:22

Reporter	TomR	Assigned To	thraxisp
Priority	normal	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	fixed
Fixed in Version	0.19.1

Summary	0004648: Assign To independent of $g_update_bug_threshold
Description	It would be nice to have a own threshold for Assign To: ( $g_update_bug_assign_threshold ) so that you're able to change status and assign issues without having update rights. Than it would work like $g_set_status_threshold.
Additional Information	See also 0004603
Tags	No tags attached.

thraxisp 2004-10-01 11:16 reporter ~0007863	Will add a new config variable $g_update_bug_assign_threshold. If this is not defined, it will default back to the old $g_update_bug_threshold for backwards compatibility.

thraxisp 2004-10-01 12:58 reporter ~0007868	Upon more detailed inspection of the code, this already exists. $g_handle_bug_threshold controls the Assign To: list. $g_update_bug_threshold controls whether the user can update the bug content. You probably want to re-open 0004603 if this does what you intend.

TomR 2004-10-01 16:11 reporter ~0007869	I do not fully ubderstand what you're saying, it already exists. I want reporters to be able to change status and to assign issue, however I do not want them to update the issue. They should only be able to use the two buttows ( and dropdowns ). However when g_update_bug_threshold = UPDATER, then the Assign To: button is not visible while the Change Status button is visible. That was the reason for a $g_update_bug_assign_threshold varaible, which should control the visibility of the Assign To: button.

thraxisp 2004-10-01 20:28 reporter ~0007870	The $g_handle_bug_threshold controls the content of the Assign To list. The issue is the Assign To button doesn't show up unless you can handle the bug ($g_update_bug_threshold). I believe that you are looking for another threshold to show the Assign To button. I get it now (I think).

TomR 2004-10-02 03:35 reporter ~0007871	Yes, that is what I mean, however does it make sense to you? Our reason is that we would like to 'forward' a issue to someone ( perhaps with only an additional note ) but not to update anything from the issue, except change status.

thraxisp 2004-10-02 09:49 reporter ~0007874	Fixed in CVS

TomR 2004-10-06 03:30 reporter ~0007931 Last edited: 2004-10-07 04:25	The visibility of the Assign To: button is now controlled by $g_update_bug_assign_threshold, however when you try to update the AssignTo field with the button, I get Access denied. Probably because of $g_update_bug_threshold My situation: $g_update_bug_threshold = UPDATER $g_update_bug_assign_threshold = REPORTER $g_handle_bug_threshold = DEVELOPER; $g_set_status_threshold = array(FEEDBACK => DEVELOPER, ACKNOWLEDGED => DEVELOPER, CONFIRMED => DEVELOPER, ASSIGNED => REPORTER, PROGRESS => DEVELOPER, RESULT => DEVELOPER, RESOLVED => REPORTER, CLOSED => DEVELOPER); I want a REPORTER give the ability to assign a bug to a a DEVELOPER, and/or change status to ASSIGNED/RESOLVED. Even when the REPORTER does not have 'update' ability he/she is able to change Status, but not to change Assigned To. edited on: 10-06-04 03:33 edited on: 10-06-04 03:33 edited on: 10-07-04 04:25

thraxisp 2004-10-08 13:55 reporter ~0007962	The access level checks are now more accurate to allow this. Fixed in CVS.