+1 

Columns resizing should be available. 

+1

I truly can´t believe you cannot adjust the column width

+1

The issue is removing the column next to the cell that contains an extra-long description of the AD account being pulled from AD  via script. 

Is anything happening here?

In my dashboard - it is completely inconsistent.  Two different Jira query tables, same field in the same order, different column width of summary.

It appears, to get maximum column width, you need a big URL.  Otherwise the column width is shrunk to the largest word...  (This assumes you have a lot of fields you are reporting on).

+1

Each time I decide to add sprints to be displayed in a column in the issue navigator, a piece of me dies. 

+1

+1

+1

+1

+1

+1

+1

+100

is that issue related also to Jira cloud?

+1

+1

+1

+1

+1

Are there any workarounds for this that people know of?

+1

+1

+1 - after 15 years ... what's the holdup?

+1

Please provide a way to do this.
This could help to give my customers a quick state of the project.
E.g. Some of my state-names are longer and they are truncated in the list.

if somebody has develop the plugin or have some idea to develop this plugin,please let me know.let's do it.

+1

Pretty Please!

guys, this is from 2005. 43 comments and 148 votes. how much more interest do you need?

+1 this is a simple thing for reporting purposes.

Just wasted 1 hour of my time trying to find an answer to how to change column widths, as couldn't believe it's not a function available.  Even some explanation on why Jira choosing to wrap text for some fields, and no others of similar lengths.  

Please consider this, for basic users - it's something that will delight instead of frustrate them.   

Side question: does anyone know how many votes are roughly needed to even get Jira team to look at this?  

Since it has been 13 years, I developed a solution that adds extra effort but works for me.  For the multiline fields that tend to get a lot of text, I pre-insert a invisible table and specify the width.  When users add the text and save, the specified width carries over to the Issue Navigator.

comment

+1 please!

+1 for this feature.

I can't believe that THIRTEEN YEARS after this was requested, it still hasn't been done.

(Well, OK, to be honest, I can believe it, because this is Jira we're talking about.  Customer feedback goes into a black hole.)

But still, even for Jira, this is egregious.  It's hard to think of a piece of software that displays data in tables that doesn't have this simple and straightforward functionality, whether with drag handles on the columns or a way to set widths by numbers or whatever.  If the Jira code is so bad that this can't be done without breaking everything, then maybe it's high time to throw away the Jira code and start over.

+1 for this feature (laptop and pad user)

+1 for this feature.

We also urgendly need this feature for users in our company who have only small (12'') screens in order to allow focusing on columns of interest.

If we cannot provide a state of the art view the tool will not be accepted and thus be dropped.

Without this feature, lists in Jira are practically unusable.  Come on.  what products now a days don't have column resizing that sticks and is even somewhat intelligent?!

Yet another MUST HAVE feature that has been open for YEARS!

+ 1 for this feature

Same here. I've moved to the new Jira interface and the Issue Navigator still wants to autowidth columns according to some algorithm. In my case, I need to see Labels, but can't because the Label contents are being truncated because the column width is too narrow.

becoming a huge issue for us, hard to believe this hasn't been addressed since originally posted.

I need a fix for this, my screen is not big enough to see past the descriptions bc they are too long, and barely wrap.... i would like to see the full column list... please update ASAP!  How on earth is this ticket closed?  

+1 New user trying to learn the system and wondering why this function is not available.

+1 still relevant Today

+1 I've had problems with the columns randomly resizing down to where there is no space between the key and the description which makes it extremely difficult to read and select keys to copy/paste. This would fix that problem, or you could fix the resizing so it doesn't remove all the whitespace, or you could make it so linking can find issues even when they aren't recently viewed.

+1  Hard to believe this is not supported!!!

Yes please make this. Having several filter results above each other is a pain because they wont line up.

how about instead of working on your details view you listen to your customers and add a simple column resizing function in the list view, which is clearly what alot of your customers use, since they are requesting this change.

Little things like this, are what jira is lacking.. Jira is a very powerful tool but its held back by simple things that are mind boggling why they have not been implemented and still not implemented 10 years after the issue was raised..

When you work on large projects which have replaced your excel trackers sometimes you need to still visibly view the issues in the same way excel presented them.

Jira is great, apart from the hundreds of little let downs which sometimes makes customers question why they invested so much money in an application that cant do something excel has done for nearly 20 years?

Hi everyone,

When we originally redesigned the search UI in JIRA, ability to view and take action on certain fields directly from the search results was a must have. Rather than continuing to present a list of issues with each field as a column, we made a deliberate choice to embed the full issue view within the issue navigator. The result was the https://confluence.atlassian.com/display/JIRA/Using+the+Issue+Navigator#UsingtheIssueNavigator-DetailView, which has been available since JIRA 6.0.

We do not plan to make major investments in the list view as we continue to iterate on the detail view.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

Good question.

Hi Roy.. does what you pasted here mean you'll add this feature any soon?

From my experience, don't hold your breath!

I don't think I'm alone in still being the only user to want this feature implemented.

Any chance we could get an update to see if this is something on Atlasian's radar?

I am asking the same question to JIRA support.
How can we do this? How can we specify the width of columns? You should tell us through JIRA workflow how to make this type of change while creating new custom columns.

Regards,
Venkat Guruvelli
Voice: 803-898-2934

From: Lucas Boczkowski (JIRA) jira@atlassian.com
Sent: Wednesday, July 24, 2013 12:45 PM
To: Venkat Guruvelli
Subject: [JIRA] (JRA-6034) Be able to specify the width of columns in the Issue Navigator

https://jira.atlassian.com/secure/useravatar?avatarId=10612

Lucas Boczkowski<https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/secure/ViewProfile.jspa?name%3Dlucas.boczkowski%2540tarjetanaranja.com.ar&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=e61d0ebe6a5ab681fd4789b17d284a889adbefa4ac98bd477bb9d8fb22dbd01f> commented on an issue

Hello Venkat.
How can we do this? How can we specify the width of columns?

Cheers.

JIRA<https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/browse/JRA&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=5c3076391d38cd890012e25dff9823d29324fcbeb8122b7df7caf274f937e5f5> / [Improvement] <https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/browse/JRA-6034&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=b47d981d56c45600ac78375e903c1a06763e507acbcb641ce85adfbc3e901d71> JRA-6034<https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/browse/JRA-6034&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=b47d981d56c45600ac78375e903c1a06763e507acbcb641ce85adfbc3e901d71>

Be able to specify the width of columns in the Issue Navigator<https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/browse/JRA-6034&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=b47d981d56c45600ac78375e903c1a06763e507acbcb641ce85adfbc3e901d71>

[Add Comment]<https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/browse/JRA-6034%23add-comment&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=379da3ecf95d2ee9c2d42ff55fbcea43d110f776fe5db440f9a015f9e5a6321b>

Add Comment<https://urldefense.proofpoint.com/v1/url?u=https://jira.atlassian.com/browse/JRA-6034%23add-comment&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=379da3ecf95d2ee9c2d42ff55fbcea43d110f776fe5db440f9a015f9e5a6321b>

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira<https://urldefense.proofpoint.com/v1/url?u=http://www.atlassian.com/software/jira&k=L5G5zaSmVxhL3ZBjCgAA0A%3D%3D%0A&r=zFHIJ47%2FKE2K%2F1lH12oBptaqnIXV9iUvmQa%2B56W6crk%3D%0A&m=kO74dLOB6lyLA0cJPFfVckKKlRrH5xZDypBJx8xMxfE%3D%0A&s=9188b7c38474ba5eb5a71fd0faa6de9bf5344adac6bf297f1d449906dea12db6>

[JIRA logo]

Confidentiality Note

This message is intended for the use of the person or entity to which it is addressed and may contain information, including health information, that is privileged, confidential, and the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this information is STRICTLY PROHIBITED.

If you have received this in error, please notify us immediately and destroy the related message.

Hello Venkat.
How can we do this? How can we specify the width of columns?

Cheers.

Users are able to CLONE -Data Columns while defining custom columns and show them in the Issue Navigator

JRA-6034 Users are able to specify the width of columns while defining custom columns and show them in the Issue Navigator

Unbelieveable that no action has been taken so far. Since JIRA 5.1 the Due Date column uses 3 (three!) lines in the Issue Navigator - removing other columns does not help...

I agree.. this has been open forever and should be a relatively simple thing to implement...

This has become such a hot topic that we would be unlikely to upgrade from our existing JIRA (4.2.1) to any JIRA release which did not have this functionality.

If Atlassian cannot be bhtered to address this, they should come clean and tell their customers and preferably tell us why!!

We just upgraded to JIRA 5.0 and I am very disapointed that this feature is still not implemented. So we can link team members in comments, which is nothing more than a close to useless marketing feature, but this important usability feature is still ignored? Way to go!

just moved to jira and this echo evas comment, a seemingly simple fix either to have field attribute defining column width or allow width to be altered on viewer. Again setting width to field description seems sub optimal

I cant believe this is open in 2005, and we are now in 2012, and yet this STILL isnt fix. Let me understand correctly, this shouldnt be a HARD fix, like other ones that had been opened since 2003. I dont get why isnt this fix 7 years later when it seems like a 1-day fix that is important for client deliverable (else why would we need printable feature) or any presentation to the senior management team. Having like a line wrap on Summary just make the report look longer and just "ugly" (quoting from our users).

This has been open since 2005 and still not resolved. That's disappointing because it's the number 1 complaint about Jira in the large organization I work for. Hope it gets fixed soon.

I completely agree, this is very annoying. It would be very useful to have column width user-defined.

This change would be EXTREMELY USEFUL for our team. It's very difficult to view the information we need to see easily without excessive scrolling. This is one of the reasons I like to do work in Excel vs. JIRA - I can control the formats there and it's easier to read through 250 issues.

This feature is still missing in JIRA 4.4 - it would be a great enhancement to have adjustable width columns.

Currently our customer fields have a description which when contain a good amount of detail, makes the columns extremely wide. If we could have the capability to resize the columns, or have the description text wrap or have the option to not show the desciptiont ext at all, that would be very useful.

This can look ugly on browser windows with small realestate. I suggest using jqGrid, it has all resizing capabilities along with scrolling.

http://www.trirand.com/blog/

Try the demos
http://trirand.com/blog/jqgrid/jqgrid.html

I am in no way affiliated with jqGrid, I just use it

The browser best fit is a good start but sometimes you get field entries that are just too long and upset the entire table (wasted space in the other fields in the columns, columns pushed horizontally off the page). Other times there are fields you aren't really interested in their full values, it's good enough to know they have values. And I just hate having to scroll sideways to see everything (and I don't have a small screen). All this is why I wrote the GreaseMonkey script. When I feel motivated to add new functionality to it I'll clean up the code, maybe even port it to IE7Pro and remove the GM dependent code so it can run in Opera (course I don't have opera so who knows how well that will work). I'm not a system admin running a copy of Jira, I'm just a user of one of your customers.

See JRA-14428 for s GreaseMonkey script that allows one to do this. Please note that GreaseMonkey only works in Firefox browsers.

The browser's "best fit" is generally good enough, but I've just come across a situation in which it fails miserably to create a visually pleasing fit.

My example: I have three large text columns Summary, Description and Mitigation plan, as well as three small fields (Status, Impact and Trend). The Summary and Description fields are using the bulk of the horizontal space. Mitigation plan has been allocated very little space, despite the fact that it has a lot of text. This leads to a very narrow and extremely tall column for Mitigation plan. Is it possible that the "best fit" approach breaks down at some point?

If this is at all possible, then we should ensure that the width is also preserved in different Navigator views, such as excel.

This looks especially bad if you have several sub-tasks and try to include that in the navigator columns. It would be really nifty if the Description field could somehow take size precedence, as its the field that typically has the most information, and yet becomes small.

Peter,

There is no way of changing the column size explicitly at the moment. Currently your browser will do a "best fit" of the columns, which isn't always great. I'll log this as an improvment request.

Cheers

Mark C