Quick Add Menu is Getting Decluttered

[Boyan Iliev]

What adds to the frustration is that we were par of the "test group" and I've contacted support to explicitly exclude us due to mentioned issues. It seems like the feedback we provided to defend our request never got any attention as I see the same comments now that the feature is live - either make it optional, or configurable.

[Nia Yanes Barreto]

This has become a great source of frustration for users in my organization. They are getting confused regarding where things like checklists and links are located. This also adds extra work for admins as we have gotten several messages asking the same question of how to disable or where their buttons are located now.

[Dwight Holman]

We also hate the new UI/UX.

In our case we found the drop-down list includes redundant items (we have disabled whiteboards), and that without that item in the list we *should* get the individual buttons instead of the horrible "Add" button.

You can follow and vote for the backlog item here: JRACLOUD-85144

If they fix this it won't help orgs that use whiteboards :-\

[Ahmud Auleear]

Hi Everyone, 

Thank you for sharing your feedback on the recent UI changes. I understand that these updates have impacted your workflows, and I genuinely appreciate your candid responses and suggestions.

The decision to adjust the quick add on menu stemmed from two main considerations. First, feedback from many users indicated that the previous issue view was overly cluttered, which led to confusion and increased cognitive load, decreasing ease of use. Second, with the continued growth of the Atlassian suite, the prior design, originally built for a limited set of buttons, struggled to keep pace with our expanding array of objects, products, and integrations. This has impacted both usability and discoverability across the issue view.

We are closely reviewing your suggestions around pinning or favouriting essential actions to enhance accessibility and maintain the speed you rely on.Your feedback is instrumental as we continue refining this experience, and we’re committed to making improvements that align with your needs.

Please continue to provide feedback. 

Best, 

Ahmud 

[Alex Kras]

Thank you for reading/response!

[Dwight Holman]

For those following this thread, you might want to watch or follow this one: JRACLOUD-85131

Not sure why @Ahmud Auleear didn't mention this.

[Jef Verheyden]

As others have mentioned here, 
We have a lot of negative feedback from our users about this sudden UX change.
We expect similar negative feedback for the other UX changes in the pipeline if we dont have a better way of ease our users into it.

[Adam Janecke]

@Dwight Holman nice work! I just voted on this! 

[JRACLOUD-85131] Allow choosing the Quick actions style - Create and track feature requests for Atlassian products.

Other people on this thread should do the same. 

[Kim Raffield]

I triage jira bug tickets and ship them to dev teams backlogs all day long, and am constantly dealing with large numbers of duplicate issues which require me to link the issues, as well as migrate over attachments and relevant information included in the duplicated ticket. Additionally I'm formatting the body of tickets all day, every day. Now every action I take to do my job takes 2+ clicks: formatting text, adding an attachment, linking a ticket. This is really frustrating and inconvenient. Please reconsider, or at the very least make this an optional setting.

[David Holman]

Two pages of comments already 🤣

I keep wondering if Atlassian just needs more experienced Product Mangers and Designers or if top-down management is strangling their ability to deliver.

Even if the mess of this change wasn't self-evident, a day of user testing would have revealed the issue. Maybe user testing is just a checkbox item for them now 🤔

If this managed to pass user testing because the wrong test audience was used, a small pilot roll-out would have triggered the response we're seeing here … just on a much smaller scale.

Come on, Atlassian, we're all trying hard to stick with you. Work with us.

[Jens Schumacher]

To add another vote for this. I was trying to add a goal to an issue and thought the feature wasn't enabled for some reason. Turns out it's located under "Apps". This really doesn't a whole lot of sense and requires another round of thought and iteration. 

[Dwight Holman]

The comments here reminded me that Atlassian has yet to add a keyboard shortcut for "Link issue" which is another suggested feature you might want to follow and vote for JRACLOUD-74885.

[Florian Ratz]

This is not decluttering, this is enshittification. 

[Rune Rasmussen]

Before we had some handy dandy buttons readily available, each with their own singular purpose.
Now we have a "+ Add" button and just fucking oodles of empty space doing nothing.

And when I click on the "+ Add" button I get all the buttons that used to be readily available.

This is not an improvement.
Please Atlassian. Function over form!

[Lara Bailey]

@Dwight Holman thank you!
https://community.atlassian.com/t5/Jira-articles/Quick-Add-Menu-is-Getting-Decluttered/bc-p/2861292#M16356

I voted for it: pinning by admins on project-level and users on the user-level looks like a good solution. There is indeed so much empty space, and so much lost in speed and awareness if the space is not used.

I also voted to add keyboard shortcuts for "linking" issues you mentioned, despite it would not solve the biggest problem with hiding the "Link" button: If users no longer see the button, they'll use it less. Shortcuts are only useful for superusers who use Jira so much that they know how to use it and want to use it more quickly.

@Ahmud Auleear would be great if you could add that link to the main article, since it's buried in the second page of comments

[Graham Douglas]

This change has resulted in tickets not being linked properly (instead of proper links users are just adding links in comments or description fields as they can't immediately see the link button). You've hidden away key functionality that should be 'in your face' for a user. At least allow this feature to be toggled on / off as we didn't have a clutter problem to solve in our organisation and i would expect many others to be in a similar position. 

[Erica T_]

And yet again, another feature that should have the option to enable or disable. You see the comments at how this is not helpful to many of us and why, the extra clicking is just unnecessary and time-consuming and you roll it out anyway. All I can figure is your own developers do not use Jira, otherwise, they wouldn't have let you do this.

Those of you on this thread, in case you aren't aware, brace yourself for another feature that should have also been optional, this will be disruptive to those us of who used the URL field that actually need to see the URL itself but now won't have a choice but to alter the way we use fields and the automation that goes to them. 

[Stephan Grubbe Sølby]

Jira is slowly but surely becoming a pain to use. This latest change give all my teams an extra click for adding sub-tasks, links etc.  

Not only are you violating basic UX rules and design patterns, you even prevent users from configuring Jira to best support their workflow and use the product so it suits them best.

Pretty please with sugar on top: Stop implementing "features" that affects all especially, when they are extremely bad and without ways to configure/disable them.

You must add an option so I am allowed to control which buttons I want visible and available on my issue view. 

[NiYunfan]

Any UI change may affect many users. Here we have some user complaint about it when creating sub-tasks.

Please give jira admin a chance to customize the buttons, or give end-user a chance to swith to old view

Thanks!

[Yannis Caff]

Bump. 

This still sucks

[Abbey Ortlieb]

This is the worst update - the only way to add a subtask to an issue now is from the search/"issue" view. Why would you remove that ability from the issue itself or even from backlog views? Now if someone needs to add a subtask to an issue they are looking at, they first have to open a new tab/window and SEARCH for the issue they were already looking at. 

I'm all for decluttering, but you can't remove essential functionality from the thing it is essential to.

[Kim Raffield]

Months later, and still, numerous times a day, I am fumbling in the menu looking for which option I need to link another jira ticket. Not only does this still suck tremendously, the options in the dropdown between linking an existing issue, an external webpage or confluence look so similar I routinely click the wrong one.  

[André S_]

Once upon a time there was a device called Palm Pilot.

It had a small screen and limited computing resources.

There also was a book titled "Palm OS Programming Bible" by Lonnon R. Foster.

In Chapter 6, Making Fast Applications he says:

"Always try to reduce the number of taps required to perform a particular action."

and

"buttons provide the quickest access to a program's functions […]
push buttons are faster than pop-up lists, requiring only one tap instead of two to make a selection"

This is still true despite the book being written in 2002 for a completely different platform.

I wish UI/UX designers would take the first quoted sentence as their primary mantra.

Atlassian seems to go the completely opposite direction. ☹

[Jared Moore]

~4 months later and I am still finding myself annoyed by this "improvement" on an hourly basis. Please give us the option to opt-out!

[Tobias Viehweger]

Also banging this drum again - as a Marketplace vendor we actually needed to built an UI / explainer for our customers because it's now easy to miss where you can find our app in the issue. 

Please add customization options / pinned buttons for admins, this would improve the UX of this massively.