• Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 3.12.2
    • None
    • Viewing filters

      This never happened in the older versions, we have just upgraded after 2 years and the date fields wrap for no apparent reason.

      There is plenty of room for no fields to wrap yet they still wrap.

      I'll attach a screenshot

        1. global-static-min.css
          21 kB
        2. screenshot-1.jpg
          screenshot-1.jpg
          175 kB
        3. screenshot-2.jpg
          screenshot-2.jpg
          243 kB

            [JRASERVER-14642] Data Columns Wrapping Unnecessarily

            Eva added a comment -

            For 4.4 onward, the problem now lies in Summary being wrapped. I found 6034, which STILL isnt fix and I was wondering if there is a CSS File i can change to make it work.

            Eva added a comment - For 4.4 onward, the problem now lies in Summary being wrapped. I found 6034, which STILL isnt fix and I was wondering if there is a CSS File i can change to make it work.

            Ok,

            Im happy with my CSS workaround.

            Dale Fraser added a comment - Ok, Im happy with my CSS workaround.

            AntonA added a comment -

            Due to the reasons described by Michael, I do not think we will be able to fix the problem such that it meets the expectations and requirements of all customers. There are too many variables at play here: customisable columns, quite a few various date formats, a large number of web browsers. Unfortuantely, it looks like JRA-6034 is the viable option.

            AntonA added a comment - Due to the reasons described by Michael, I do not think we will be able to fix the problem such that it meets the expectations and requirements of all customers. There are too many variables at play here: customisable columns, quite a few various date formats, a large number of web browsers. Unfortuantely, it looks like JRA-6034 is the viable option.

            Hi Dale,

            I have been investigating this issue for a bit of time now, and I've come to the conclusion that the reason the date columns wrap comes down to Internet Explorer's specific way of determining table column widths. None of Safari, Firefox and Opera exhibit the same behaviour under the current circumstances.

            The question of "Why does Internet Explorer do this?" is a difficult one to answer, since it's hard to get that kind of information. Here's what we know:

            • we specify a "1%" width for all of the header cells in the table and "20%" width for the summary text cells.
            • the status, resolution, assignee, reporter and issue key columns are set to have their text not wrap (white-space: nowrap)
            • notice that the created, updated and due date columns are absent from the above list

            So my theory is, because we have specified explicit widths for all columns, but the widths do not add up to 100%, Internet Explorer needs to decide what to do with the excess width, and perhaps because the summary column has a far larger width than the rest, it decides to add the bulk of it there, and since the created and updated columns are allowed to have their text wrapped, it does not mind shrinking them down to a size which will make them wrap. This is of course highly speculative.

            In terms of coming up with a solution to this problem which will solve it in every case, this would be a very difficult task, due to the configurable nature of the issue navigator and the arbitrary nature of the data to be displayed. However, if you want to guarantee for your issue navigator that certain columns will not have their values wrapped, we can achieve this with a simple CSS change. I have attached a patched version of the global-static-min.css file from JIRA 3.12.2 which contains the following modification:

            Old
            #issuetable .status, #issuetable .resolution, #issuetable .assignee, #issuetable .reporter, #issuetable .issuekey
            {
            	white-space: nowrap;
            }
            
            New
            #issuetable .status, #issuetable .resolution, #issuetable .assignee, #issuetable .reporter, #issuetable .issuekey, #issuetable .created, #issuetable .updated, #issuetable .duedate
            {
            	white-space: nowrap;
            }
            

            Using this new file will ensure that the created, updated and due date columns do not have their values wrapped. Of course, you should only use this patched file if your original CSS file has not been modified, otherwise you will lose your changes. Also note that the attached file has been minified, which means it will not be easy to modify by hand, so if you need to make additional modifications, you will need to do the following:

            1. modify the global-static.css file in /src/webapp/styles
            2. minify the file and write the output to global-static-min.css
            3. restart JIRA

            Also note that to apply the patched file that I have provided, you will need to restart JIRA and flush your browser's cache.

            I hope this helps you solve your problem.

            Cheers,
            Michael Tokar [Atlassian]

            Michael Tokar added a comment - Hi Dale, I have been investigating this issue for a bit of time now, and I've come to the conclusion that the reason the date columns wrap comes down to Internet Explorer's specific way of determining table column widths. None of Safari, Firefox and Opera exhibit the same behaviour under the current circumstances. The question of "Why does Internet Explorer do this?" is a difficult one to answer, since it's hard to get that kind of information. Here's what we know: we specify a "1%" width for all of the header cells in the table and "20%" width for the summary text cells. the status, resolution, assignee, reporter and issue key columns are set to have their text not wrap ( white-space: nowrap ) notice that the created, updated and due date columns are absent from the above list So my theory is, because we have specified explicit widths for all columns, but the widths do not add up to 100%, Internet Explorer needs to decide what to do with the excess width, and perhaps because the summary column has a far larger width than the rest, it decides to add the bulk of it there, and since the created and updated columns are allowed to have their text wrapped, it does not mind shrinking them down to a size which will make them wrap. This is of course highly speculative. In terms of coming up with a solution to this problem which will solve it in every case, this would be a very difficult task, due to the configurable nature of the issue navigator and the arbitrary nature of the data to be displayed. However, if you want to guarantee for your issue navigator that certain columns will not have their values wrapped, we can achieve this with a simple CSS change. I have attached a patched version of the global-static-min.css file from JIRA 3.12.2 which contains the following modification: Old #issuetable .status, #issuetable .resolution, #issuetable .assignee, #issuetable .reporter, #issuetable .issuekey { white-space: nowrap; } New #issuetable .status, #issuetable .resolution, #issuetable .assignee, #issuetable .reporter, #issuetable .issuekey, #issuetable .created, #issuetable .updated, #issuetable .duedate { white-space: nowrap; } Using this new file will ensure that the created, updated and due date columns do not have their values wrapped. Of course, you should only use this patched file if your original CSS file has not been modified, otherwise you will lose your changes. Also note that the attached file has been minified , which means it will not be easy to modify by hand, so if you need to make additional modifications, you will need to do the following: modify the global-static.css file in /src/webapp/styles minify the file and write the output to global-static-min.css restart JIRA Also note that to apply the patched file that I have provided, you will need to restart JIRA and flush your browser's cache. I hope this helps you solve your problem. Cheers, Michael Tokar [Atlassian]

            Not sure what version exactly, your site doesnt tell me and the old server has been decommisioned.

            This might help.

            Name Cogstate
            Type JIRA Professional: Commercial
            SEN SEN-114907
            Maintenance Expires 08-Sep-2005

            Since the Maintance expired 08/09/05 then it would have been a version of Pro from 08/09/04.

            Dale Fraser added a comment - Not sure what version exactly, your site doesnt tell me and the old server has been decommisioned. This might help. Name Cogstate Type JIRA Professional: Commercial SEN SEN-114907 Maintenance Expires 08-Sep-2005 Since the Maintance expired 08/09/05 then it would have been a version of Pro from 08/09/04.

            AntonA added a comment -

            Dale,

            May I ask which version of JIRA you have upgraded from?

            We need to have a closer look at this.

            We have had a few issues with formatting of Issue Navigator columns in the past. It is very difficult to make them work as one expects (which also varies from customer to customer) in all supported browsers (Firefox, IE, Opera and Safari) especially given the large number of configurable variables, such as date/time formats.

            We will take a closer look. I would like to know what has changed. However, we may not be able to find a good solution to this.

            Cheers,
            Anton

            AntonA added a comment - Dale, May I ask which version of JIRA you have upgraded from? We need to have a closer look at this. We have had a few issues with formatting of Issue Navigator columns in the past. It is very difficult to make them work as one expects (which also varies from customer to customer) in all supported browsers (Firefox, IE, Opera and Safari) especially given the large number of configurable variables, such as date/time formats. We will take a closer look. I would like to know what has changed. However, we may not be able to find a good solution to this. Cheers, Anton

            Ok,

            I seriously believe that those classes used to exist and were removed in a recent version or something else in the css changed. I added the following to the min version of the CSS as the one you said above does nothing.

            #issuetable .created

            { white-space: nowrap; }

            #issuetable .updated

            { white-space: nowrap; }

            Prety straight forward, this fixes the problem, but I think this should be fixed in a release as I will loose this next update.

            Dale Fraser added a comment - Ok, I seriously believe that those classes used to exist and were removed in a recent version or something else in the css changed. I added the following to the min version of the CSS as the one you said above does nothing. #issuetable .created { white-space: nowrap; } #issuetable .updated { white-space: nowrap; } Prety straight forward, this fixes the problem, but I think this should be fixed in a release as I will loose this next update.

            AntonA added a comment -

            Thanks for the update.

            The "#issuetable .summary" is the class for the summary column. The updated and created columns do not have a specific style defined.

            We will try to reproduce and get back to you.

            AntonA added a comment - Thanks for the update. The "#issuetable .summary" is the class for the summary column. The updated and created columns do not have a specific style defined. We will try to reproduce and get back to you.

            And I am using IE7

            Dale Fraser added a comment - And I am using IE7

            That is because you are using a different date format.

            If I use that format it works for me also. Because a SPACE is larger than a / and takes up a few more pixels and causes the wrapping. My tests have shown that this

            dd/MMM/yyyy works
            dd-MMM-yyyy doesn't work
            dd MMM yyyy doesn't work

            You can see even here the the difference is only a couple of pixels. I have done a lot of HTML in my time and I don't see how a 20% value would produce this result, as that column is no where near 20% the width of the screen, you could easily see this in the screenshot. And where tables are defined as % widths they auto size best fit and this isn't happening as the Summary field is very large and has a lot 30% extra space. So perhaps the problem lies in the width being specified on the summary that the others need to squash to allow room.

            Are you sure that is the correct class as the HTML says <td class="nav updated"> and I can't find any references to updated in the css.

            Dale Fraser added a comment - That is because you are using a different date format. If I use that format it works for me also. Because a SPACE is larger than a / and takes up a few more pixels and causes the wrapping. My tests have shown that this dd/MMM/yyyy works dd-MMM-yyyy doesn't work dd MMM yyyy doesn't work You can see even here the the difference is only a couple of pixels. I have done a lot of HTML in my time and I don't see how a 20% value would produce this result, as that column is no where near 20% the width of the screen, you could easily see this in the screenshot. And where tables are defined as % widths they auto size best fit and this isn't happening as the Summary field is very large and has a lot 30% extra space. So perhaps the problem lies in the width being specified on the summary that the others need to squash to allow room. Are you sure that is the correct class as the HTML says <td class="nav updated"> and I can't find any references to updated in the css.

              mtokar Michael Tokar
              52df2149ea8b Dale Fraser
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 3.5h
                  3.5h