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
> > 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
> > 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