Labels: Type-Defect Priority-Medium
New issue 3011 by matthew....@kitware.com: allow closing requests but not
What version are you running?
What steps will reproduce the problem?
1. Grant 'change request status' but NOT 'can edit request' to a user.
2. Try to close a request as that user.
What is the expected output?
Request is closed, and user closing the request can enture a close message
(or at least can provide one when closing via API).
What do you see instead?
From web page: nothing happens.
From rbt: "rbtools.api.errors.APIError: You don't have permission for this
(HTTP 403, API Error 101)"
Please provide any additional information below.
I would really like to be able to designate certain users as 'merge
masters', however I do *not* want to grant these users permission to
arbitrarily make changes to other users' requests (e.g. branch,
description, etc.). Right now there does not seem to be a way to do this.
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/groups/opt_out.