Hello Ryan, Thanks for looking at this, I've added a new patch to deal with:
> * Forwarding the values of all select fields in the form See: https://issues.apache.org/bloodhound/attachment/ticket/617/preserve_qct_fields_all.diff I will look at point 2 next to ensure a ticket is created at the correct path according to the Product selection. As a note, the QCT form displays "Version" and "Type" fields when accessed from a page that is a child of /main/products/ but does not when accessed as a child of /main/x. I'm I correct in assuming this is correct behavior as "Version" and "Type" field values are product specific? If so, is the "Product" field redundant on the QCT form when accessed from /main/products/x? Please note preserve_qct_fields_all.diff does not appear to work for QCT forms outside main/products/some_chlid . I'm currently looking into this. Cheers, Antony On 9 December 2013 06:56, Ryan Ollos <[email protected]> wrote: > On Sun, Dec 8, 2013 at 6:31 AM, Antony Semonella <[email protected]>wrote: > >> Hello all, >> >> The following patch will fix #617: >> >> >> https://issues.apache.org/bloodhound/attachment/ticket/617/preserve_qct_fields.diff >> >> Cheers, >> >> Antony > > > It looks like a good start. I'll do some testing this morning, > > Two related issues we should consider fixing: > * Forwarding the values of all select fields in the form > * Most importantly, "More fields" should forward the currently selected > product. See comment in (1). > > (1) http://markmail.org/message/5enlgw4jsdyhce6u
