You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We've started using the "New Jira Experience" in the past week, and while it's a refreshing take on JIRA, there's a lot of seemingly odd design choices going on.
The latest one to bug my team is the Issue View. There seems to be a newly imposed maximum-width constraint on the Issue View, meaning that the content never extends beyond a specific width in the screen.
In it's default view on a regular 1080p display, there's some fairly odd padding showing up:
However when I collapse the side-bar (which I'm doing as I get more familiar with the new UI), this get's even more pronounced and starts to feel jarring:
I've some IT and Design users who're starting to use 4k monitors and on those devices it looks, frankly, ridiculous.
When we factor in JRIA Issues with screenshots and lots of text, the somewhat arbitrary-feeling restriction just makes it annoying and enforces more scrolling.
One of my team raised this with Atlassian support, and were told that this is a design choice to improve readability, while my designer interprets this as form over function - I tend to agree.
Please review this, as it's just an unnecessary headache and, as device screens get more dense, is just going to become unnecessarily pronounced.
Definitely this is a problem.
For the most part the new UI is "prettier" than the current one, however this width limit, which was added later (the "new" UI did not have this limit initially), is a deal breaker.
The issue view width limit ruins the experience on high resolution screens.
On the current UI, items are nicely spread out, and easy to read. Additionally items like issue links, branch names, confluence links, are readable.
With the new UI, we see lots more scrolling, both for the whole issue, as well as various text fields, code blocks, and comments within the issue. Also, titles in the issue links are often truncated, and there is a lot more wrapping.
With current UI:
With New UI:
Please can someone escalate and review this change before the new UI is deployed as the default UI.
It takes resizing a window to less than 1400 pixels wide before the maximum viewport limit is reached so even a standard 1920x1080 display with a maximised window is wasting creating over 500 pixels wide of dead space.
Many of the other pages in the new Jira UI are scaling nicely, surely this can't be the finished product?
This has been raised as a support ticket - https://jira.atlassian.com/browse/JRACLOUD-67884
Please comment and upvote in order for Atlassian support to prioritise it.
I would take the use of a '>' like you have on the left hand side to collapse the menu away
And woe betide you if you want a table with more than 2-3 columns. Many columns get squished so narrow that the text is almost printed vertically.
Particularly frustrating as the styles get applied a fraction of a second after the page loads, so you briefly see the table looking half-way usable, then it snaps to be stupidly narrow.
Being as it's style, evidently someone thinks it's aesthetically better, and won't budge on reverting the change, and allowing the view to go as wide as the screen allows. Guys - we have resize handles on our browsers, we can make it narrower if we don't like it wide!
This is a common use-case for our team. Diagnostic logs are often a key part of problem investigation, both for bugs and customer support. We're still quite happy on Jira Server, so I'm worried what the users will say when we migrate to Cloud...
Came here to confirm that this is still a problem (and a very unpragmatic one at that - it's just abhorrent UX design). Workaround mentioned in comments on the issue tracker works and is delightfully simple. Can't this CSS fix just be implemented as an optional feature if Atlassian is so adamant about the merits of its current issue layout?
We've done that on Jira Server - makes the product much more fit-for-purpose.