Jim, Without making perl change in gnatsweb.pl I don't think thing there is support for this today. However, you could do something like this in your dbconfig file. It's not pretty, but would probably work....but you'll need to keep an updated list of people not allowed to close a PR in here (not a great solution) I don't to this exactly, but do change other fields based on certain state changes. I didn't try this, but tweaked mine a bit for this example.... I think this would work for you to block say user kmcfarla from closing a PR. fwiw field "State" { builtin-name "state" description "The current state of the PR" enumerated-in-file { path "states" fields { "state" "type" "description" } key "state" default "open" } textsearch on-change { # Add Audit-Trail entries when this field changes. add-audit-trail # Require that a reason be supplied when this field is edited. require-change-reason } # # Change State back to its original setting for the following users aren't allowed to Close a PR # on-change "(oldpr:State[type]==\"open\") & (Originator==\"kmcfarla\")" { set-field "State" { oldpr:State } } } -----Original Message----- From: help-gnats-bounces+kmcfarland=starentnetworks.com@gnu.org [mailto:help-gnats-bounces+kmcfarland=starentnetworks.com@gnu.org]On Behalf Of Jim Prowak Sent: Wednesday, February 16, 2005 9:17 AM To: help-gnats@gnu.org Subject: restricting close PR With gnats-web, is there a way to restrict the ability to close PRs to a certain user? thanks, Jim -------------------------------------------------------------------------------------------- Jim Prowak Voice(585) 899-4306 National Semiconductor Fax (585) 899-4320 1000 Pittsford-Victor Rd. Pittsford, N.Y. 14534 jim.prowak@nsc.com --------------------------------------------------------------------------------------------