+1 Would like to see vertical space be reduced

Just moved from Trello and the (too big) Kanban card size is very frustrating.  I removed the fields - so why does JIRA insist on keeping the space?

+1 for skinny card format in kanban

For making sub-tasks half-size on the boards the following css may be used:

.ghx-subtask-group {
    display: flex;
    flex-wrap: wrap;
    padding-left:10px;
}
  
.ghx-has-swimlanes .ghx-subtask-group {
    padding-left:0px;
}

/* The next part may be used to give the first sub-task the full width. */
/*
.ghx-issue-subtask:nth-child(1) {
    margin: 0;
    width: 100%;
}
*/

.ghx-issue-subtask {
    margin-left: 0px;
    margin-right: -4px;
    width: 50%;
}

If nothing else, this may be used with Stylish.

This issue was a significant reason why I chose to go with a standalone JIRA install rather than JIRA Cloud. If it wasn't for the existence of the banner hack (thank you robertbergs) it could have been a non-starter. Presentation is a feature!

For what it's worth, I'll +1 this too

It might take some time before Atlassian decides to implement this feature.

My team has tried several options, so I hope this also helps others:

1) Install a browser addon like Stylish or similar that allows you to override websites CSS. Create the CSS to match your liking. (disadvantage: cannot automate the distribution of new CSS changes in the team)
2) Create a browser addon yourself that can override websites CSS. (advantage gained: possibility to automate updates of CSS in the team. disadvantage: all browser addons need to have a user account. it's preferred you don't use your private user - so the addon doesn't become obsolete once you change your job)
3) Create your own Jira addon that overrides websites CSS (advantage gained: addon is a shared component for the team, so anybody with enough rights can work on it. We also have automated distribution of CSS in place. Possible disadvantage: on each update of CSS you need to build and deploy the addon again)

Things to consider for number 3): In order not minimize the number of changes and deployments of the addon, put the CSS files on companies shared network drive instead of embedding it into the addon. This also means that you can have multiple folders on your shared drive, each containing CSS for different team / board, and each folder having a unique board ID as a name, so the addon will know what CSS to use per each board, by looking at the board ID.

Good luck!

+1 for this issue.

Only able to see 6 or 7 cards per screen makes this very difficult to use for planning and prioritizing.

Also, side note: it is sometimes possible to fit multiple fields on the same line (e.g. Due Date | Component) really does have to take 2 lines.

Try this: https://de.atlassian.com/company/contact/contact-ceos