On my reviewboard instance, I just mark those review requests as discarded.

Whoever is picking up this defect will then post a new review request with
their diff.
This accomplishes a few things:
 -keeps all the old history
 -is simple for me do
 -clear ownership of the change going forward

Scott Q

On Thu, May 21, 2015 at 3:04 PM, David Carson <dccar...@gmail.com> wrote:

> We have had some recent employee departures, leaving a few open requests
> owned by submitters who are no longer at the company.
>
> I don't see any way -- short of changing the underlying database -- to
> reassign these requests to another user.  Is there any such admin function?
>
> If not, and I do change the underlying database, what other fields might
> have to be adjusted as well?  I can think of the open count, which I
> haven't quite found in the db yet, but I'm sure is there.  Anything else?
>
> Thanks,
> David
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to