#727: Handle long free text entries in sending qct fields to newticket interface
--------------------------+-----------------------
Reporter: gjm | Owner: antony
Type: enhancement | Status: accepted
Priority: major | Milestone: Release 8
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-----------------------
Comment (by antony):
Replying to [comment:13 rjollos]:
> Sorry that I didn't get to review this sooner. There is a regressions in
r1570616: the product at scope is no longer the default selection.
>
> The best way I could see to fix this is with some refactoring, so I hope
it doesn't seem like I'm trying to hijack your ticket, but since we are
nearing a release it's probably easiest if I just push the fix and ask for
feedback (particularly testing).
>
> What do you think about having the //More fields// link visible but
disabled, rather than initially hidden? Actually, the only case that it
will be hidden on page load is at global scope when `[ticket]
default_product` hasn't been set, so it's probably not worth spending too
much time refining.
>
> Minor things:
> * Python source code should wrap on 79 characters. Additional style
guidelines that we follow can be found at trac:TracDev/CodingStyle.
> * !JavaScript code uses two-space indentation.
Hello the changes look good to me.
r1573926 now 'disables' the "More fields" link instead of hiding it.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/727#comment:15>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker