#727: Handle long free text entries in sending qct fields to newticket interface
--------------------------+----------------------
Reporter: gjm | Owner: antony
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by antony):
Replying to [comment:7 rjollos]:
> Having a default product for the case when //Choose...// is selected in
the //Product// select is going to become more complex in light of the
changes in #388 (comment:8:ticket:388). At least, the products need to be
filtered by permission when determining the default product in
`get_default_product`.
>
> Discussing "default product" in this context is bound to be confusing
since it is not directly related to `[ticket] default_product`, or the
concept of a //default product//, which has been (for the most part)
removed from Bloodhound in #658 (`[multiproduct] default_product_prefix`).
>
> It may be less confusing to just disable the //More fields// link when a
product is not selected. That would make the //More fields// link
consistent with the behavior of the //Create// button. It would also avoid
implicit behavior, in which we are trying to determine the best choice for
the user when they haven't yet made a choice.
Thanks for thoughts on this, I'm in complete agreement regarding the
removal of implicit behaviour. I'll update the QCT form to disable the
//More fields// link when a product is not selected.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/727#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
