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

New issue 3855 by rbt post -r ID changenum does not update the change list number in the review request

*** 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?
ReviewBoard 2.0.15
RBTools 0.7.2
Perforce 2014.2

What's the URL of the page containing the problem?

Not sure how to answer this, it's the main page for any review


What steps will reproduce the problem?
1. Create a p4 change list, cl 833 in this example,  and a new review

rbt post --target-people sallan --publish  833

2. Submit the cl and close the review.

p4 submit -c 833
rbt close 15

Note the review displays 'Change: 833'

3. Reopen the review, create a new CL and post using rid

rbt post -r 15 834

The diff gets correctly uploaded, but the change list number is not updated.

What is the expected output? What do you see instead?

I would like to see the RB page display the new change list number

Change: 834

instead of the old, already submitted change list number.

What operating system are you using? What browser?

I see this on Mac, Ubuntu, Fedora, CentOS6 using Chrome, FF and Safari.

Please provide any additional information below.

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