"New JIRA 'Experience'"

[Terrance Lopez]

Not a fan.

[Semi]

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

[Martin Wickline]

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.

https://jira.atlassian.com/browse/JRACLOUD-69044

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:

https://community.atlassian.com/t5/Jira-discussions/Can-we-make-the-new-UI-use-screen-space-more-efficiently/m-p/751548

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).