Labels: Type-Defect Priority-Medium
New issue 3778 by vlov...@gmail.com: api-cache is broken for bugs_closed?
*** READ THIS BEFORE POSTING!
*** You must complete this form in its entirety, or your bug report will be
*** If you have a security issue to report, please send it confidentially
*** secur...@reviewboard.org. Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
*** For customer support, please post to reviewbo...@googlegroups.com
*** 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?
0.7.1 & 2.0.13
What's the URL of the page containing the problem?
What steps will reproduce the problem?
1. Create a review with the API setting bugs_closed to ['1234'] in the
draft (see https://code.google.com/p/reviewboard/issues/detail?id=3777)
2. Review has a bad value for defects
3. Fix it up manually in the reviewboard website to 1234
4. Fetch the bugs_closed field via the API
What is the expected output? What do you see instead?
I expect bugs_closed to be '1234'. Instead it's the weird serialized array
still. Clearing out the apicache.db fixed the issue.
What operating system are you using? What browser?
10.10 & python2.7
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
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/d/optout.