#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 rjollos):
The patch looks very good overall. There are a few things we should
discuss.
Previously, the //Product// select would default to the product in scope
when at product scope. At global scope, it would default to
`default_product` (#304), or //Choose...// if a `default_product` has not
been set. After the patch, the //Product// select always defaults to
//Choose ...//, which will direct to the `default_product` (or the first
entry in the list of products if `default_product` has not been set) when
at either global or product scope. The behavior you've chosen is probably
good when at global scope (although see comments in #304), but at product
scope I think we should continue to select the product in scope by default
and drop the //Choose ...// entry (the latter should have been handled in
#304 to begin with). I'm going to give the behavior at global scope some
more thought though, because in the past there have been arguments for
making the select default to `default_product`.
I'm also seeing some warnings displayed. When at global scope, if the
//Product// select is left as //Choose....//, then data is forwarded to
the `default_product` form, but a warning is always displayed:
{{{#!html
<div id="warning" class="alert fade in">
<button type="button" class="close" data-
dismiss="alert">×</button>
<span class="label label-warning">Warning</span>
field product must be set
</div>
}}}
The warning is not seen when a product is explicitly selected.
The same issue occurs when at product scope, but additionally the
following warning is always seen regardless of which product is selected:
{{{#!html
<div id="warning" class="alert fade in">
<button type="button" class="close" data-
dismiss="alert">×</button>
<span class="label label-warning">Warning</span>
field component must be set
</div>
}}}
This is strange because the Component defaults to //component1// and
Component is not a field of the QCT form.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/727#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
