The new issue view page in JIRA 4.1 as currently deployed on jira.atlassian.com uses an unprofessionally-large font that results in the user needing to scroll down to view even basic details about the issue. For instance, a simple issue like JRA-18349, used to fit comfortably on one page in a browser window, but it is now necessary to scroll down just to view all of the link information, and one must scroll down a lot to see the last comment. On tickets with many links or a long description, the tickets require so much scrolling that they are very hard to read. Please significantly reduce the font size and eliminate wasted whitespace such as the large blank areas surrounding the dividing lines between sections.

      I have tested this on Firefox 3.0 under Linux and using IE 8 and Firefox 3.5 on Windows XP and all have the same issue.

        1. important_313.png
          important_313.png
          191 kB
        2. important_41.png
          important_41.png
          141 kB
        3. important_41scaled.png
          important_41scaled.png
          138 kB
        4. simple_313.png
          simple_313.png
          163 kB
        5. simple_41.png
          simple_41.png
          133 kB
        6. simple_41scaled.png
          simple_41scaled.png
          124 kB

          Form Name

            [JRASERVER-20652] JIRA 4.1 issue view wastes screen space

            Thanks for everyone's comments and feedback on this issue.

            For the purposes of keeping one main issue I will closed this and users that wish to provide further feedback can do so on the main feedback issue: JRA-20669.

            Cheers,
            Roy Krishna
            JIRA Product Management

            Roy Krishna (Inactive) added a comment - Thanks for everyone's comments and feedback on this issue. For the purposes of keeping one main issue I will closed this and users that wish to provide further feedback can do so on the main feedback issue: JRA-20669 . Cheers, Roy Krishna JIRA Product Management

            Hi Gregory,

            thank you for reporting this issue, I've raised JRA-22629 to track this problem

            Cheers,
            Peter

            Peter Leschev added a comment - Hi Gregory, thank you for reporting this issue, I've raised JRA-22629 to track this problem Cheers, Peter

            G B added a comment -

            I see this behavior on the view issue page for this ticket (JIRA v4.2#587) using Firefox 3.6.9 on RHEL5.

            I just checked Firefox 3.5.5 and IE 8 on Windows and neither exhibits the problem (the open/closed status persists.)

            Steps to reproduce:

            #. Visit http://jira.atlassian.com/browse/JRA-20652
            #. Close the "Attachments" section
            #. Click "JRA-20652" at the top of the page. Attachments is now open

            Thanks.

            G B added a comment - I see this behavior on the view issue page for this ticket (JIRA v4.2#587) using Firefox 3.6.9 on RHEL5. I just checked Firefox 3.5.5 and IE 8 on Windows and neither exhibits the problem (the open/closed status persists.) Steps to reproduce: #. Visit http://jira.atlassian.com/browse/JRA-20652 #. Close the "Attachments" section #. Click " JRA-20652 " at the top of the page. Attachments is now open Thanks.

            sladey added a comment -

            Gregory, thank you for your feedback. Regarding your comment

            but the setting does not persist across page views

            this is not the intended behaviour. Can you please tell us which sections do not have their collapsed state persisted and which browser(s) you are seeing this on. I am on Windows 7, FF 3.6.11 and the collapsed state is being persisted.

            sladey added a comment - Gregory, thank you for your feedback. Regarding your comment but the setting does not persist across page views this is not the intended behaviour. Can you please tell us which sections do not have their collapsed state persisted and which browser(s) you are seeing this on. I am on Windows 7, FF 3.6.11 and the collapsed state is being persisted.

            G B added a comment -

            I will give Atlassian some points for improving readability in 4.2 over 4.1, however the overall problem of wasting of real estate is still there, specifically in font size and the Issue Links section. Also, JIRA 4.2 teases with the ability to collapse sections that I don't care to see, but the setting does not persist across page views, so the function is essentially useless.

            The Issue Navigator improvements in 4.2 may be enough for me to come to terms with the remaining Issue View problems, but its unfortunate to have to choose.

            JIRA is not facebook!

            Yes! For better or worse, JIRA power users (especially the people who shell out the coin for your products) are Microsoft Excel users, not Facebook users.

            G B added a comment - I will give Atlassian some points for improving readability in 4.2 over 4.1 , however the overall problem of wasting of real estate is still there, specifically in font size and the Issue Links section. Also, JIRA 4.2 teases with the ability to collapse sections that I don't care to see, but the setting does not persist across page views, so the function is essentially useless. The Issue Navigator improvements in 4.2 may be enough for me to come to terms with the remaining Issue View problems, but its unfortunate to have to choose. JIRA is not facebook! Yes! For better or worse, JIRA power users (especially the people who shell out the coin for your products) are Microsoft Excel users, not Facebook users.

            Luckily I did not upgrade and as long as the UI is not changeable I won't. I realized by chance using the atlassian support JIRA that from a certain time on (the new UI) it was close to unusable. The screen only shows white space, no information. I have to scroll way way more than before.

            On the other hand, whilst the new UI is not changeable back to the old one I have an easy job as an administrator: because I know that all my users (10 persons) do not like the new look at all. My only fear is on how to migrate to a different platform than JIRA in the future sometime. Hopefully 4.0.x will supported for a long long time .... and maybe with >4.2 we will have a structured layout back.

            Although I see the "modern" of that look, a bug tracker is not a social network. JIRA is not facebook!

            Björn Schormann added a comment - Luckily I did not upgrade and as long as the UI is not changeable I won't. I realized by chance using the atlassian support JIRA that from a certain time on (the new UI) it was close to unusable. The screen only shows white space, no information. I have to scroll way way more than before. On the other hand, whilst the new UI is not changeable back to the old one I have an easy job as an administrator: because I know that all my users (10 persons) do not like the new look at all. My only fear is on how to migrate to a different platform than JIRA in the future sometime. Hopefully 4.0.x will supported for a long long time .... and maybe with >4.2 we will have a structured layout back. Although I see the "modern" of that look, a bug tracker is not a social network. JIRA is not facebook!

            We've recently upgraded to 4.1 and I'm finding this poor use of screen real estate really hampering my productivity. My eyes are having to work much harder to read the page and then all the extra scrolling to even read the JIRA description is leading to a really unpleasant experience.

            David Middleton added a comment - We've recently upgraded to 4.1 and I'm finding this poor use of screen real estate really hampering my productivity. My eyes are having to work much harder to read the page and then all the extra scrolling to even read the JIRA description is leading to a really unpleasant experience.

            I use 1024x768 screen resolution on my corporate laptop(no way to change this) and it's almost impossible to use such design. My screen ended at first half of description of this issue (for example). I have to scroll all the time. In Excel I use Tahoma, 8 font to save space. Idea to set font sizes adjustable looks very reasonable for me. In fact my first reaction of new design was "Give me to change CSS now!"
            P.S. I use IE 7

            Volodymyr Matsyshen added a comment - I use 1024x768 screen resolution on my corporate laptop(no way to change this) and it's almost impossible to use such design. My screen ended at first half of description of this issue (for example). I have to scroll all the time. In Excel I use Tahoma, 8 font to save space. Idea to set font sizes adjustable looks very reasonable for me. In fact my first reaction of new design was "Give me to change CSS now!" P.S. I use IE 7

            G B added a comment -

            I'm using RedHat Enterprise Linux 5 with Firefox 3.0.14. Sadly, RedHat only supports Firefox 3.0.x with RHEL5.

            G B added a comment - I'm using RedHat Enterprise Linux 5 with Firefox 3.0.14. Sadly, RedHat only supports Firefox 3.0.x with RHEL5.

            Brett Ryan added a comment -

            I agree the font size needs to be configurable, as a per user setting.

            Most think that a larger screen means a bigger window size. I'm visually impaired with no pheripherial vision, so I must keep my window size ~900px otherwise I have to keep turning my head to see the whole window, on the new layout I must be 1022px minimum which is starting to push the limits of my visual range. In comparrison 4.0.2 has a minimum limit of 400px, that's a big difference.

            Please ensure that whatever changes are made continue to remain "accessible" for all people. My suggestions in JRA-20669 could make this new layout a lot more accessible.

            Brett Ryan added a comment - I agree the font size needs to be configurable, as a per user setting. Most think that a larger screen means a bigger window size. I'm visually impaired with no pheripherial vision, so I must keep my window size ~900px otherwise I have to keep turning my head to see the whole window, on the new layout I must be 1022px minimum which is starting to push the limits of my visual range. In comparrison 4.0.2 has a minimum limit of 400px, that's a big difference. Please ensure that whatever changes are made continue to remain "accessible" for all people. My suggestions in JRA-20669 could make this new layout a lot more accessible.

              Unassigned Unassigned
              3f85ab128771 G B
              Affected customers:
              27 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: