I can't really give you advice here, because any customizations you make
today are going to make it harder to debug problems you'll inevitably hit
with the database schema down the road.
I'll make it a priority to get proper extension support for customizable
fields in for 1.7.2 (or whatever the next 1.7.x release is with new
features). There's work that needs to be done before this can go in, so I
will have to finish that work up first, but then it should be easier for
you both to do what you want to do without modifying Review Board itself or
its database schema.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Dec 27, 2012 at 2:49 AM, maris <02c...@gmail.com> wrote:
> Thanks Christian for your reply.
> I am adding a new entry in review detail page.
> I have added new model in reviews app and did modify the corresponding
> template, but while selecting and publishing we are facing issue. We
> understood that these details are first saved in draft model and on
> publishing will be saved to original model.Could you please tell what files
> to be modified in order to achieve this.
> Please tell us the work flow.
> On Wednesday, 26 December 2012 12:25:10 UTC-8, Christian Hammond wrote:
>> Internally, review requests now allow custom metadata. I have an
>> in-progress change to add API support for this, so maybe in 1.7.2. I'd like
>> that to land at the same time as the work needed for custom fields in the
>> UI, though.
>> On Dec 26, 2012, at 12:20 PM, Matthew Woehlke <mwoehlk...@gmail.com>
>> > On 2012-12-26 14:56, Christian Hammond wrote:
>> >> I'm hoping to create a sample extension for this in time, but
>> honestly, there's work that still needs to be done for this. The extension
>> support we added is intended to be experimental and incomplete, and we'll
>> be adding to it over time. I imagine we'll start to make custom fields work
>> well in an early 1.7.x, but I don't have a date for you right now, as there
>> are things we have to get to before we can do this well.
>> > Is it possible yet to add fields that can only be read/written via the
>> API? It's a bummer if we can't see the name of the request branch on the
>> web interface, but if we can get/set it through the API, I could at least
>> write a functional 'git rb merge'.
>> > --
>> > Matthew
>> > --
>> > Want to help the Review Board project? Donate today at
>> http://www.reviewboard.org/**donate/ <http://www.reviewboard.org/donate/>
>> > Happy user? Let us know at
>> > http://www.reviewboard.org/**users/<http://www.reviewboard.org/users/>
>> > -~----------~----~----~----~--**----~----~------~--~---
>> > To unsubscribe from this group, send email to reviewboard...@**
>> > For more options, visit this group at http://groups.google.com/**
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at