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.
Have Atlassian considered a way to let all Jira users know about these kind of UX changes to avoid the confusion and requests to IT about why changes have happened? This is not the 1st time we have been surprised by sudden changes that are not expected or explained and had to web search for more information
With lots of other systems, there is a pop-up that appears with What's New when you try to interact with a control that has changed.
Atlassian Team members are employees working across the company in a wide variety of roles.
August 18, 2026 edited
Thanks, everyone — we're reading all of this.
First, I appreciate the detail in these comments. This is exactly the kind of feedback that helps us, even when it's tough to hear. I want to acknowledge what we're consistently hearing from you so you know it's landing, not disappearing:
Fields are hard to tell apart : missing borders/boundaries, low contrast, placeholder-as-label, and accessibility concerns around field distinction and tab order. Actively working on this
Formatting is harder to reach: the rich-text toolbar isn't obvious at create time. Actively working on this
Lost context: custom field descriptions/help text no longer showing. We implemented info icon to store all the field descriptions so that nothing is lost
App compatibility: ScriptRunner Behaviours not firing on the new screen. This one we're actively investigating. For account-specific issues (ScriptRunner behaviours, permission errors, a partial/odd rollout state), please also raise a support ticket so we can reproduce against your real configuration.
I can't share fixes or timelines in a forum post, and I won't pretend everything's solved but every one of these is captured and being reviewed by the team. I'll reply to your comments individually below.
Thank you for sticking with us and helping make this better.
@Jake Ramsley _PTC_ Thank you Jake — this matches themes we're hearing consistently: fields not being visually distinct, the formatting toolbar being harder to find, and custom-field descriptions not showing. All are on our radar and under active review. A screenshot of the custom-field-description case especially would help us
@EDelPriore_SD Thanks for flagging. The set of fields that can be pinned to the quick (collapsed) form is currently limited, and Status not being available. The full form still exposes it
I hear you on the muscle-memory cost, Armin — that's come through strongly and I won't pretend the transition is frictionless. The current way to go back to old experience is as follows -
Admins can also revert their site to the previous create experience via Settings > System > General Configurations, then set "Simple Create as Default" tooff. This applies to the entire site
Compatibility with ScriptRunner Behaviours on the new create screen is something we're investigating. So it's tracked against a real configuration, could you also raise it through support? That helps us reproduce your exact setup. and @Blum_ Volker _Extern_ : can i know your ticket_id? Team is looking into your support ticket
@Dave Mathijs Thanks for candid feedback. The fullform can be accessed by clicking on the "Show More" icon in the header
Appreciate the detailed list, Thorsten. Uniform-looking fields and harder-to-reach formatting are consistent themes we're actively reviewing. Three dots menu appear when the create modal has been expanded to fullform. It doesn't show up in quick create. If there is deviation from this behavior, can I please ask you to raise a support ticket with us directly?
It's a gap we've captured. While our evaluations for formatting toolbar are under way, may I request you to (A) simply drag and drop the local files into the create modal or (B) use `/` command to invoke various options and select Image, Video or File option to upload files from local system or (C) use Attachment field.
@Kanad Dagaonkar Good on ya! This is the first time I've seen the Atlassian Team respond like this when things didn't go as planned. It is definitely appreciated from my side of the fence. This type of dialog is what should happen, especially when a new feature is planned for release. I think the fact that it was released into the system as the default without an explanation of how to reverse it was your biggest issue. People are less likely to flame you when you are open and are more likely to provide constructive criticism if it isn't forced on them one morning when they open up the tool.
@Rob Sher I mentioned this in another post regarding this change, but here is the latest answer to your question about new releases/changes to the Cloud UI.
It used to be a newsletter you could subscribe to called Cloud Release Notes: I even think it was originally titled Tl: Dr. Mind you this admin stuff isn't my full time day job so I took that to heart and only read through it when I had some time. 😜
I do not see a way to subscribe to updates but at least there is something to go digging through.
Lastly, if you are an admin, you now have the ability to see what updates will affect your instance in your admin section. Here is the post about how to get there. View all changes to an Atlassian app
As proof that I missed it originally, I used the new admin feature and lo and behold, there it was.
Search for "Simple create as default" and set it to Off.
Save your changes and refresh your browser.
This is what I did and I hope that this new layout will not become the new default. THisis why I did not open a support ticket to check the scriptrunner problems.
@Danno Thanks for this. Good to know, but this doesn't really solve the problem. Still feel these kind of key UI changes should be called out in the user experience when they go live. Other companies do it
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.
@Rob Sher the crazy thing is that Atlassian has new feature callouts in the UI all the time and the logic behind when they do or don't display those is a mystery.
@Kanad Dagaonkar - thanks, it sounds like things are moving in the right direction, but I think your list is missing the point that several people made about it really not being obvious which Space or Work Type you are creating an issue for any more, or that you can change it.
Regarding your point 3, I hope the info icon isn't the end of the fix for the hidden descriptions/help text, because I would consider that to still be hidden from most users.
Can I also recommend you point your designers towards this article: What are Affordances? — updated 2026 | IxDF , especially the part on hidden affordances, because there are a lot of them in this new design.
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.
Hey @Kanad Dagaonkar - first, thanks IMMENSELY for the engagement here - as others have mentioned, this is not what we've been trained to expect but its AWESOME and I love it! I truly believe this is how we all succeed.
I feel terrible "thanking you for your engagement" by being negative, so I want to make it clear that none of this is personal. It just feels like the 3,986th time I've given pretty much "this exact feedback" and nothing seems to change, even when we're told they will ... and that's a very frustrating place to be. If there's an off chance that someone will listen, I'm going to take it! So without further ado (and my apologies)....
There is no problem being solved. This is another change from Atlassian that does not seem to be grounded in anything. The first post contains a section titled "Why this change?" but the "problem" being described is not with the "create issue" functionality - its that the person writing doesn't know how to use "Screens". If a user is overwhelmed by a ticket's create screen that's their admin's fault, not Atlassian's. If you are compelled to do something here, the fix would be making screens easier to manage, not "break the create screen".
The solution is legitimately worse. If admins can already remove fields which aren't relevant to the request being created, then it would follow that what's left would be relevant (at least according to the admin). By not showing these fields by default, this choice is taken away from me, replaced with the option to either make a field required or have the majority of users ignore it.
It feels like there's not an understanding of how people use Jira behind this. One of the explicit benefits mentioned for this change is "Field visibility customization as a Jira user". This might be a spicy take but...why should a user of an enterprise-class work management system be given the ability to hide fields? I can think of a lot of reasons why an admin would want to "force show" a field, but not a lot many which require letting a user override that.
This doesn't get a formal bullet because there's a chance it's just me not understanding, but it doesn't feel like this was part of any "seasonal release" - TBH I still feel like we're getting a flood of constant changes. If it was, then apologies and thank you.
My honest opinion is "there's nothing wrong with the create screen; this needs to be undone and thrown away."
@Kanad Dagaonkar - I know you mentioned not being able to commit to timelines in the public comment threads, but are there any publicly visible tickets we can follow along on some of the upcoming changes you've mentioned?
Some of these missing features, such as borders around the fields & low contrast, are high-impact accessibility issues for folks with visual impairments or processing differences such as dyslexia. I'd like to be able to direct my team to follow for updates, or at least be able to get notifications myself to pass along. Thank you!
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.
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.
"As always, Jira administrators tend to comment on changes from their perspective, not from that of the end users. Our users think it's great."
Wurm Peter I would agree that administrators tend to worry about things from their perspective, but I would argue that they probably have a more balanced perspective than the end user.
Put another way, "Looking out for the end user's experience" is something I would 100% consider part of my remit as a Jira admin, but I don't expect end users to worry about "ensuring that ticket submitters provide as much information as they can so that the help desk can action their ticket as quickly as possible."
76 comments