Hi Everyone!

I'm excited to share that we have now rolled out the column resizing feature to all Jira Cloud instances on the Continuous (normal) release track, so I will be going ahead and closing this Suggestion.

Please note that if your instance is on a Bundled release track then it may take longer for your instance to receive this feature. Keep an eye on the release notes for more updates.

Hi 01563aad1b42,

This change will not impact the JSM Queues, this request is only focused on the global Issue Search page and the "Issues" page on projects.

It looks like there's an existing request for JSM Cloud queues here, if you'd like to Vote and Follow that: https://jira.atlassian.com/browse/JSDCLOUD-7842

Hi Tyler,

Will this also effect the Service Management Queues?

Kind Regards,

Jake

Hi Everyone,

Thanks for your patience on this request. I'm excited to announce that we are starting to roll out an updated design for the Jira Issue Search page which includes the ability to resize the columns in the List View.

In order to resize a column, click and drag the right border of a column. Alternatively, select the More actions (︙) menu on a table header, then select Resize column.

Most Cloud instances should receive this update in the coming weeks, however if your instance is on a Bundled release track then it may take longer.

Please note that column resizing and the updated design are only available in the New Issue Search. If you have opt-out to the old search experience and would like to try the updated design, you can return to the new experience using the Meatball menu in the top right of the page and clicking "Switch to the new issue search".

It's no option for me to use the new Issue Navigator as I need to see all the relevant information at a glance. With the new version, even after having reduced the number of columns, I need to scroll just to see the status of the issue or to find out how much time was spent on it. This is an enormous waste of time and not an improvement at all. Please find a way to reduce the column size to fit everything on one screen as before.

I've had to resort to going back to the old search results UI as the new one just takes up too much space for some columns. 

What used to fit neatly into one screen now requires two and me scrolling left and right to see needed information. 

From what I can tell, the new UI has preset widths depending on the field type. Not very convenient if I'm using a field to hold three char codes and the column is taking up 60 spaces. 

I think this has become more pressing since its creation 20 years ago.....

With the latest updates to issue search, we are seeing more issues with columns randomly being excessively wide. 

Everyone in my company has opted to revert to the old version of search while we still can because the new version has only been a headache. 

It is unfortunate that Atlassian has chosen not to allow column widths to be modified.  It is cumbersome in dashboards and other reporting/viewing options to be forced with a fixed length.  

I wanted the fix version to be first however it takes up most of the box.  see image. This is not very helpful

@dmeyer@Atlassian.com 

+1

+1

+1

@Nicole Geske - go to this suggestion - it's the same thing and still open.  Vote for it.   Same for anyone else still watching this one.  They haven't made it very clear that it's been duplicated into another open suggestion.  

Yes this is very short sighted, it's about the most efficient use of the product and without this functionality it is hard to be efficient. For me (JSD), users submit long titles as the Summary, the text in that field is wrapped and makes my table/search results/queues hard to read and significantly longer. Instead of a succinct table, I get a super wide column for reporter (b/c some have email addresses) and a super narrow, yet wrapped column for Summary. So most entries are three or four rows tall plus some of the columns that I want to see but are of low priority are nice and wide which is a waste of space, I'd rather expand them when I need to see the rest of the information. 

Here's the use case. I really think you are missing the boat here. Multiple times per day I need to filter 4000+ issues for key words and then scan a list of 60+ search results to find an old project that touched specific programs. I need to be able to scan the list quickly to see if any of these "hits" matches what I am looking for. I do not want to scroll through 60 "full" views within the navigator. I want the grid view and I'd like to change column sizes according to the content of the field I am looking at. Thanks.

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?

As working in Excel came up multiple times, let me mention that the Better Excel Plugin preserves the manually set column widths in Excel exports.

If that gives you a better view or you primarily want to share the tabular view, just create a XLS template file, set the column widths in Excel and the add-on will this up with issue data without changing the column widths. (The built-in issue-navigator.xlsx template does an "auto-fit" on the exported table, but this can be turned off. Your custom templates will not "auto-fit".)

• See the customization guide

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