0011454: [patch] Allow forcing assignment on report

ID	Project	Category	View Status	Date Submitted	Last Update
0011454	mantisbt	bugtracker	public	2010-02-02 08:52	2010-02-05 01:12

Reporter	am-gtz	Assigned To
Priority	normal	Severity	feature	Reproducibility	always
Status	new	Resolution	open
Product Version	1.2.0rc2

Summary	0011454: [patch] Allow forcing assignment on report
Description	Sometimes it is necessary to force an issue to be assigned directly when it is reported. For this we added a new configuration setting to make the handler_id field a required field.
Tags	No tags attached.

am-gtz 2010-02-02 08:59 reporter ~0024287	the patch can be found here: http://git.mantisforge.org/w/mantisbt/gtz-et.git?a=shortlog;h=refs/heads/mantisbt-issue11454

jreese 2010-02-04 14:00 reporter ~0024320	As an alternate to requiring the assignment field (esp when some configurations may not show the field to certain users), would it be possible to replace the user assignment with auto-assigning based on categories? That method is already implemented in MantisBT, just requires assigning a user to each category in the project.

am-gtz 2010-02-05 01:12 reporter ~0024324	I know the feature to auto-assign certain user's based on the category but this is not sufficient in our case (user's are assigned mostly on "how has time to do it" basis) Actually there are several other fields that can be made required even if they are not shown. It might be useful to add a config-check or to un-require a field if it is not shown. But nevertheless I think the patch is useful (at least for us) and I guess it might be also useful for others.