public inbox for
 help / color / mirror / Atom feed
From: "McFarland, Ken" <>
To: "Jim Prowak" <>, <>
Subject: RE: restricting close PR
Date: Wed, 16 Feb 2005 18:40:00 -0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 2188 bytes --]

Without making perl change in 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.
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"
    on-change {
        # Add Audit-Trail entries when this field changes.
        # Require that a reason be supplied when this field is edited.

    # 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" {

-----Original Message-----
From: []On Behalf Of Jim Prowak
Sent: Wednesday, February 16, 2005 9:17 AM
Subject: restricting close PR

With gnats-web, is there a way to restrict the ability to close PRs to a certain user? 


Jim Prowak                                                           Voice(585) 899-4306   
National Semiconductor                                      Fax (585) 899-4320    
1000 Pittsford-Victor Rd.
Pittsford, N.Y. 14534

[-- Attachment #1.2: Type: text/html, Size: 5741 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

             reply	other threads:[~2005-02-16 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16 18:40 McFarland, Ken [this message]
2005-02-19  5:16 ` Mel Hatzis
  -- strict thread matches above, loose matches on Subject: below --
2005-02-17 21:32 Jim Prowak
2005-02-16 14:46 Jim Prowak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).