#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):
{{{#!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>
}}}
This can be resolved by setting the product value to that of the default
product when left as ''Choose....''. I'll submit a patch for this.
Regarding:
{{{#!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>
}}}
The QCT form at product scope contains a number of hidden input fields
with empty values, '''component''' being one of them - thus failing
validation and hence the warning. It would be good to discuss which hidden
input fields are required for the QCT form at product scope.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/727#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
