Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 3811 by deleting a depends on request raise an issue because changedesc still reference it

*** You must complete this form in its entirety, or your bug report will be
*** rejected.
*** If you have a security issue to report, please send it confidentially
*** Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
*** For customer support, please post to
*** If you have a patch, please submit it to
*** This bug tracker is public. Please check that any logs or other
*** that you include has been stripped of confidential information.

What version are you running?
server 2.0.13

What's the URL of the page containing the problem?
any "view review"

What steps will reproduce the problem?
1. create a main review request X and publish
2. create a review request Y (test with draft only)
3. assign Y as a dependency of X and publish change
4. delete Y from admin database dashboard
5. display X (review) raise an internal error 500 (it looks displaying X review gets all changedescription including the one adding request Y as a dependency and since it does not exist anymore => not found) Displaying diff does not raise the issue because changedesc are not looked within.

What is the expected output? What do you see instead?
at step 4, deleting Y should remove any reference to Y in X changedesc?

What operating system are you using? What browser?
firefox linux

Please provide any additional information below.
workaround is to remove changedesc containing this Y "depends on" change from review request linked object list

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 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to