I have a lot of features in the parking lot, sometimes I have a lot of features in a release and want to see them all on the screen at once. If I could adjust the width of the columns and then have all of the features move and "tile" within the adjusted space it would make it easier for me to view the entire list of features. While this isn't a critical feature, it would help make things easier.
Thank you for your idea. The Features board is designed with fixed width columns to allow many releases to be viewed on the page in an organized way. One option for reorganizing the data when you have a large list of features would be to create a pivot table. You could use various feature details like tags or status to lay your backlog out in a more horizontal order.
Given this workaround and other current priorities, we are unlikely to implement this idea at this time.
We use the order of items in a release in a board as the priority of development.
On a 1080P display I see 6-7 items before I have to scroll.
This makes it frustrating to re-prioritise each item. (Some releases have at least 30 items in.)
Being able to widen the columns and fit more items in vertically would make reprioritising much more efficient. (And enjoyable.)
Alternatively, a mechanism to reprioritise items in a release available elsewhere in the interface would help. Tools like Jira allow the backlog to be reprioritised efficiently.
I would second Matthew's comment. With the increased adoption of ultra wide monitors in 21:9 aspect ratio, monitors are getting shorter but wider in contrast to 16:9 and 4:3 monitors of yesteryear. I can squeeze 13" ipad in the middle of the screen and work unimpeded but I'm sure that wasn't the intention. Jokes aside, it would great if this could be considered again in the future. Thanks.
While I understand the response and unlikely status of implementation, I wanted to call out the significant value of this capability. With today's larger monitors, there is a significant amount of wasted screen real estate when working with a small number of releases. We work with larger, but fewer releases, so having a few columns dedicated to one release would make prioritization easier. The way these are handled in a ZenHub board would be a good example for comparison.