You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2014/02/10 10:03:32 UTC

Re: [Apache Bloodhound] #727: Handle long free text entries in sending qct fields to newticket interface

#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):

 attachment:post_qct_fields__disabled_more__remove_hidden.diff {{{ POSTS
 }}} to the ''/newticket'' ticket form in preview mode. In addition the
 ''more'' link on the QCT form has a {{{ visibility: hidden }}} style until
 a '''Product''' has been selected - we may wish to discuss the styling of
 this.
 When within product scope, clicking ''more'' will strip the hidden fields
 that bring rise to validation error messages that are irrelevant to ''QCT
 more fields''.

 In terms of maintainability, I'm not entirely happy with my solution of
 keeping an array of fields to remove, see:
 '''post_qct_fields__disabled_more__remove_hidden.diff/bloodhound_theme/bhtheme/htdocs/js/theme.js#L102'''
 Currently I'm considering refactoring
 [source:trunk/bloodhound_theme/bhtheme/theme.py#L515 theme.py#L515] to
 indicate which hidden fields to ignore for the ''QCT more fields''
 preview. Any suggestions regarding the removal of these fields would be
 appreciated.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/727#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker