Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


"New JIRA 'Experience'"


Not a fan.

1 comment

Semi Kefi [demicon GmbH]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 14, 2018

Sorry, but this is really not a discussion! ;-)

It ought to be.  The wasted horizontal screen space and inability to display more than 5-8 words per line in a custom text field make it virtually unusable.  We were able to get around this by reverting back to the old UI styling for a time, but now this is really impacting us.  One of our team members took initiative to create a Chrome plugin to help us deal with that poor styling choice as a workaround, but now even that plugin workaround is not working.  We can't do our work effectively because of this change.  This is really horrible for usability of the product, and we cannot fathom why this was done or seen as beneficial.  See ticket for screen shots and commentary.


Many of us have given feedback through the standard JIRA "Feedback" links, we've created a ticket, and also a discussion thread, but aren't seeing any feedback from Atlassian indicating acknowledgement that this is a big problem for customers:

I can't imagine anyone who actually uses JIRA with custom fields for doing real work actually likes the new complete waste of horizontal space, and inability to resize that space when resizing the browser window.  What usability expert came up with that and thought, "Yeah, that's great.  People will definitely love all the extra whitespace that they can't get rid of?"

The Description field doesn't behave the same way as custom text fields, but it isn't a reasonable workaround to tell people they have to use the Description field for everything and no longer make use of custom text fields for organizing or separating useful information.  Why not make the custom text fields resize properly, and not waste as much space, just like the Description field?

Finally, what possible benefit can this new wasteful UI styling provide?  If they're after mobile-friendliness, that can be done without wasting real estate and different styles can be applied selectively to different user agents, without sacrificing display/usability on a primary usage modality (PC browser).


Log in or Sign up to comment