I don't really see the benefit, but if there are some framework benefits then I understand why the work is done. So I am not 100% against the changes, but there are definitely some challenges with the UI.
Everything looks the same. There is no indication what is selectable, what is editable, etc. Above there was a comment about people not knowing how to change issue type, and I didn't realize until seeing that comment that that was even possible.
Personally, I would like some indication of fields vs headers. I don't get this "make everything white/same as the background approach". Borders or background shading just makes it much more clear where the field is.
Placeholder text isn't distinguishable enough from user entered text.
Summary + description behaves differently from other fields. Other fields have a header + a field. Summary has just a field. Description has just a field. Makes it seem like the description is the summary field.
Formatting in the description field is gone. The result is users are creating the issue, then updating to format the description correctly. This causes more email (and our internal notification) noise.
Custom field descriptions are gone. Our workflow, like all companies, is not 100% standard out of the box. We have some custom descriptions explaining what they are set to or when not to fill them in. This information is no longer present on the new UI.
I'm hoping the UI can be cleaned up and improved for usability. I've been dragging my feet writing up issues today because the UI has been such a chore to work with.
This is a great feature but currently I can't promote the most important field, `status`, to the quick form mode bottom bar. In the full creation window, users can select the status (we allow all transitions) but I can't add the base `status` field in the screen editor, and thus I can't get the status field to show up on the quick create button. Is there a solution to this?
I was greeted by the new Jira Create interface today, and I honestly don't understand why this change was necessary. The previous interface has worked well for years, and changing such a fundamental part of the workflow forces users to relearn muscle memory for no clear benefit.
Please focus on improving functionality and adding genuinely useful features rather than changing interface simply for the sake of change. These kinds of UI changes have a real impact on users' productivity and workflows and there should at least be an option to retain the previous experience.
It definitely did mess up ScriptRunner Behaviours on the create issue screen. We used behaviours to fill the description with a template for Bug, Story, etc work types during creation; now it does nothing.
Open to suggestions on how to solve this in a company-managed project, as automations and post functions are triggered after the ticket is created.
Lorenzzi Bassoto July 2, 2026 I keep thinking about the impact these changes could have on ScriptRunner Behaviours that affect the create screen. It could definitely get messy.
is there any chance to withdraw this nonsense??? We use scriptrunner behaviours for hundreds of fields in issue types and now.... without any need any without any notice you change the layout and our scripts do not work anymore. I will open up a siupport ticket richt away - your behaviour is unprofessional - to say the least.
What is the tab order structure? From the short video it appears that it makes you more dependent on mouse clicks instead of being able to tab through. Also, the expanded version feels less accessible since I can't initially see field boundaries, differentiate descriptive from field text, or locate myself as easily. Plus, why did the text get so light? The contrast makes it hard to read. Last, the iconography does tell you something, but only if you knew what the fields are and can make translation, otherwise it's a bunch of pictures that either look like junk or you have to think about to understand. It's not really a guide, because I don't really care what type of field it is, I just want to get to it.
Does anyone have concrete experience with how this works in the new format or with setting up the screens to be friendly for the new format? We immediately set it back to simple create since several people were reporting it as a problem.
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 Champions.
Our create experience just changed in the past 24 hours or so but it feels like a partial implementation of this streamlined experience. The Description field has no toolbar and the Space and Work Item Type fields are no longer drop-down menus but I don't see the super slim "just Summary and Description" view described in this article as I still see fields like Status and Components.
I'm very displeased that new issue creation has been oversimplified. I can no longer include a non-image attachment in the description when creating the issue. I first have to create then go back in and edit to add an attachment into the description itself.
This is a frustrating change that slows down my workflow.
After clicking "Exit full screen", you're presented with a pop-up window that is larger than the previous "full screen" pop-window, where you have a "Minimize" link:
After which, you get this:
Atlassian, please, just give me back a full create window.
The following are clearly bugs instead of "streamlines" user experience. Additionally, at least for me I don't even see the dotted menu to be able to default opt-in to the maximized create screen. So your own docs are outdated already and you made things even worse than last month?!
Everything looks the same.
Formatting in the description field is gone.
Funny thing is, the very annoying changes to the in-app notification system you implemented a few weeks ago are not going to be fixed. Those spam me all the time with at least some of my own changes I'm not interested in to be notified about in-app. Now you make things additionally worse and I need to do extra clicks when creating new work items and be more careful to properly hit all the same-looking lines of fields.
62 comments