From: Christian Hack <christianh@ed...> - 2004-10-11 12:59:54
I've just noticed that REPORTER users don't have the ability to set the
priority of a new bug/issue. Instead, the level required to set a priority
is controlled by handle_bug_threshold. This defaults to DEVELOPER.
So a REPORTER user can't set a priority when reporting a bug.
According to the comment in config_defaults_inc.php this parameter defines
the "access level needed to be able to be listed in the assign to field"
Now I don't want every reporter listed in the "Assign To" field but I do
want them to set a priority when reporting a bug.
Why was it done like this? Is there a possible way around it? Currently I
have commented out the check in bug_report_page.php and
From: Victor Boctor <victor@fu...> - 2004-10-12 09:26:12
> I've just noticed that REPORTER users don't have the ability to set
> priority of a new bug/issue. Instead, the level required to set a
> is controlled by handle_bug_threshold. This defaults to DEVELOPER.
I agree with your point that the handle_bug_threshold should not be used
for this check. A threshold should be added which indicates that a user
has access rights to set/update issue priorities. We may even want to
check that for users who can update issues. So a user may be able to
update an issue, but not update its priority.
I suggest you report this into the bugtracker. Also if you would like
to implement it and submit a patch, that would be even better.
I suggest 'update_priority_threshold' as the config option name. The
default value should probably be the same as the default