Comment #7 on issue 2713 by matiso...@gmail.com: Reviewer, not author,
should mark issues as resolved/reopened
"most bug tracking tools allow reporters to close their own issues"
This usually can be set up in project settings. Regardless of this
statement a reviewer is always able to re-open an issue in such tools.
There are two options for him now, each of them has disadvantages:
1) Add a comment to the existent dropped/resolved issue - code owner can
just miss it because it is not indicated in the opened issues list. So "no
unresolved issues" -> "can submit the code" scheme is broken.
2) Add new issue - no connection with previous issue is supported by RB. So
all arguments should be duplicated or searched somewhere.
The current use model is inconsistent because of more general architectural
flaw. RB does not have elaborated roles and permissions support. A PM can't
be confident that the standard workflow that he set up is followed by
engineers. Engineers can't be confident whether they are following formal
procedures if they are allowed to do everything.
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.