You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Olemis Lang <ol...@gmail.com> on 2013/10/07 20:34:37 UTC
Re: [Apache Bloodhound] #618: Parent/child updates for QCT
On 10/7/13, Apache Bloodhound <de...@bloodhound.apache.org> wrote:
> #618: Parent/child updates for QCT <select />
[...]
>
> > Prioritize work on this ticket considering [http://goo.gl/NiZ96W this
> message].
>
> I don't suppose we could stop using shortened links where they are not
> necessary?
>
> The thread in question appears to have been silent after [http://mail-
> archives.apache.org/mod_mbox/bloodhound-
> dev/201309.mbox/%3C523B38B1.9010104@wandisco.com%3E this message]
jftr , links to archives.apache.org like the one above are not
rendered correctly by e-mail clients hence being hard to follow ...
> which
> suggests the following behaviour for QCT fields:
>
> * On page load, QCT forces the user to make selections;
> * Immediately after a ticket submission, the QCT retains the previous
> ticket selections for some specified timeout;
> * If the QCT is reopened before the timeout ends, the timeout is ignored;
> * If the QCT is again closed instead of submitting, the timeout is reset.
>
That's ok . Nevertheless I think it's worth to mention that the
initial aim of this ticket was to update component / version / ...
fields in QCT after changing product selection so that fields included
in form submission requests will match the definitions in selected
product context ... but I guess this will be the next move .
PS: From a QA perspective I'm not sure that we can write a functional
test atm for this kind of dynamic client-side JS behaviors .
--
Regards,
Olemis - @olemislc