hi martin,

you're absolutely right! the corner field certainly does what i want. it wasn't clear to me when reading through the card style configuration that corner fields and normal fields are different. perhaps because the corner field is configured only for the card view, though it affects all views. my only gripe now is that the corner field greatly reduces the area available for the ticket summary. if the corner field could be configured to only show up on mouseover, that would be pretty spiffy. i think i'll just stick to my custom CSS solution for now

thank you for your time, martin! i do appreciate it.

Hi Mike,
Thanks for your detailed explanation and screenshots.
It would seem to me that using List view in the Task Board with the assignee set as the corner field would fulfil your request. Corner field configured currently by adding for the Card layout, in GH5.2 this is clearer than previous versions.
Currently, the main difference between the Summary and Card are that the Summary shows no labels.
We will look at improving the spacing of the card views but I believe the list view with corner field as mentioned above is the best solution.
Regards
Martin

here are three screen shots illustrating my issue:

jira-task-list: short and sweet. concise, but i'd like to see the owner as well.
jira-task-summary: modified summary view with just issue summary and assignee. but looaaaads of extra space!
jira-task-summary-expected: what i'd expect a shortened "summary" to look like.

imho, the summary and card views are so close in size as to be interchangeable. for a sufficient number of tickets, both the summary and card views are near useless for visualization.

hi martin,

as i said in my initial comment, i am using the list view. but i would like to also see the assignee. just the summary and the assignee. that's all i want to see. so i am switching back and forth between the two views many times a day which, imho, defeats the point of a customizable view.

i am attaching three images illustrating what it looks like in the list view, what it looks like in the summary view, and how i would expect it to look like in the summary view (by changing the explicit height styling from 12.8em to 8em on all gh-issue elements). actually, you know, i think i just solved my own problem. i'm just going to use a browser plugin to override the CSS on this page with my own styling.

I'm not suggesting the issues being displayed should be moved around to best fit based on fields to display, which I realise my photoshopping may suggest, simply that the any row height be that of the card with the maximum text, while that card displays the minimum possible white space.

Even if the idea of a minimum row height based on the largest card is impossible, the image I provided shows 5-6 examples of cards/summaries with the little to no white space. Currently every card I have on screen has wasted white space, like screenshot-1, regardless of the amount of text, and fields, there is always wasted white space eating up screen real estate.

Hi Dave,

This is not possible, issues are not displayed in sequence of height/field count, and there are many variables which require all issues are the same dimensions.
Regarding your idea, how would this look if 332 and 323 were swapped? Or how would this look in that sequence if the column could show 3 (or any number of) issues per row?

Regards
Martin

Please excuse the less than excellent photoshop job. Provided as an visual representation of the idea.
Cheers

Cory, Mike,
Thanks for the screenshot.

Mike, you mention "using the kanban view to track the progress" but the screenshot shows Outline view. However, the issue sizes will be the same in either view though vertical space is saved in Compact/Kanban view since issues are not nested under their parent.

Is there any reason you don't use the List view here?
The Summary and Card views have minimum heights so that if empty or sparsely populated they still look like cards.

Bill,
Please refer to this issue regarding improvements to the List view:
http://jira.atlassian.com/browse/GHS-2313

Regards
Martin

The line view has become slightly blotted as well, now twice the old size

Also, I thought I'd point out that there's an explicit "height: 12.8em" in the div that represents the ticket in the document.