Mailing-List: contact bloodhound-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Apache Bloodhound" <bloodhound-dev@incubator.apache.org>
Cc: bloodhound-commits@incubator.apache.org
Auto-Submitted: auto-generated
Date: Mon, 08 Oct 2012 10:45:04 -0000
Reply-To: bloodhound-dev@incubator.apache.org
Subject: Re: [Apache Bloodhound] #206: Ticket fields layout broken if custom
 textarea fields are declared
Message-ID: <070.6105720ef51e786ac4bfbbd3e15c1299@incubator.apache.org>
References: <055.3aad184346ff404cdf6a648e382463f9@incubator.apache.org>
In-Reply-To: <055.3aad184346ff404cdf6a648e382463f9@incubator.apache.org>

#206: Ticket fields layout broken if custom textarea fields are declared
------------------------+-----------------------------------
  Reporter:  olemis     |      Owner:  olemis
      Type:  defect     |     Status:  accepted
  Priority:  blocker    |  Milestone:  Release 2
 Component:  ui design  |    Version:
Resolution:             |   Keywords:  ticket field textarea
------------------------+-----------------------------------

Comment (by jdreimann):

 Replying to [comment:9 olemis]:
 > The only change I suggest is to move description box to the top .
 Candidate locations are
 >
 >   1. Above enum ticket fields (e.g. immediately after ''new
 enhancement'' in attached screenshot)
 >   1. Beneath first row (e.g. between ''priority'' and ''milestone'' in
 the picture) or second row (e.g. between ''milestone'' and ''version'') of
 enum ticket fields .
 >   1. Beneath all enum ticket fields but on top of text and textarea
 fields (e.g. between ''bool field'' and ''cc'' in attached screenshot).
 >
 > Feedback is welcome .

 I wouldn't move it at this point. It may eventually make sense as an
 administration option to order all ticket fields though.
 In general the ticket fields are there to give a quick overview of the
 state of the ticket, without having to dive too far into it - therefore
 the description should come after them by default.

 To combat the issue of the description field almost disappearing off
 screen (shown in your screenshot), I believe we should reduce the
 top/bottom margins between the rows. We should also try and make the gap
 between the `keys` and `values` smaller, to make it easier to read.
 Potentially we could wrap items that are too long into a second line?

 It's also much less of a problem in the default layout without many custom
 fields.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/206#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker