I have a feeling this is what happens when a few manglers put their heads together and decide to "do something with AI" because it's the new current thing and then push it out the door without any testing.

For some users, their "create dialogue" is a complete jumbled mess with the description field (the most important one) found under "more fields".

9c0a7920250f 
I don't have this setting available.
Could it be because the support already disabled the feature globally for me before in the database?
And why did you create only a setting just for this only setting and not a general option for admins to activate/deactivate Jira lab features as requested in JRACLOUD-84103. So this solves only one symptom, but not the source of the problem.

Hi everyone,

We are happy to let you all know that we’ve been listening to your feedback, and the feature you requested is now live!

If you find that this feature doesn’t fit your team’s needs and you prefer to disable it across your Jira instance, simply follow these steps:

1. Go to Settings > System in Jira.
2. Select Edit Settings.
3. In the Options section, adjust the settings to turn the feature on or off as needed.
4. Click Update to apply your changes.

By following these steps, you can control the visibility of this feature in the "Create Issue" form.

Thank you for your continued input. If you have any further feedback or questions, we’re always here to help.

Amira Badran

Product, Jira

This is a horrible feature, which confuses our users and cause plenty of additional support effort. Please make it at least manageable globally

Hide unused fields when creating issues is a terrible feature that doesn’t even work as it should. For example, our Description field is not mandatory because in some cases, it's really not needed. However, in 90% of cases, users fill it in.

But for some reason, the Hide unused fields when creating issues feature decided that this field is rarely used and hides the Description in the unused fields. How did it conclude that it's rarely used if it's filled in 90% of the time?

As a result, users who now have this field hidden stopped filling it out because they can't find it. Moreover, in some projects, we use pre-filled templates in the Description depending on the issue type. When the Description field gets hidden, the template switching doesn’t occur.

This significantly impacts the work of our company.

I urgently request that administrators be given the ability to globally disable this feature for all users. I cannot force a large number of employees to go into their personal settings and disable it there.

This is a bug, not a feature and a good example about bad product design

Atlassian product managers forgot, that most projects are company managed and process driven

Completely agree with Andriy, here.

And It's interesting to think that Atlassian voluntarily decides this is a great feature for its users and decides to put money, effort, and resources towards it when there are tons of other essential bugs and features that are being request for years or decades. This is wild!

Cross-products overview/PO management and overall prioritization is a big problem at Atlassian. PO's are butting their heads! And we pay the price...

Our team is committed to thoroughly investigating the best way to address this need, 
and we will keep you informed if a solution becomes roadmapped.

There is nothing to "investigate", guys. The solutions are obvious and there are just 2 of them: either turn the feature off and forget about it (it's a BUG, not a feature, the only thing it does is harm users). Or add possibility for admins to turn it off for Jira instance.

I apologize for saying this, but this is just a lie. You are not "thoroughly investigating" anything. You implemented and rolled out a bad feature. It happens, we understand. Now, almost 6 months later, instead of taking some real steps like admit that this is a bad feature and roll it back, or fix it as everyone here suggests, you just posted another empty promises to "investigate" and "roadmap" a solution. Facts speak different from your words. Fact is: you do nothing about it, so your solution is to do nothing. This was your decision. Please just write that and be done with it. "We listened to you. We don't care enough to do anything about it." - that would be an honest message.

For those struggling with this "feature"; you can reach out to Atlassian support and they can disable it for your entire instance. I made the request recently and this "feature" was disabled before the end of the day. Now, the option isn't even listed in personal settings anymore.

Though this does raise the obvious question; why don't admins have the option to turn off a Jira labs feature when there is clearly a way to do it?

I've just had a team vote to abandon Jira and move to monday.com and one of the reasons stated was the addition of this feature. The team prefers a less flexible solution that is more predictable.  Having fields seemingly randomly hidden is not predictable and makes for a really bad UX.