2239430e27fb I think if there absolutely needs to be a change to be more minimal footprint on the main ticket view, another idea would be to have the "Add button" be a hover over effect that then drops down into a mega menu to show all the options and applications, so then you have one less click and you find everything all in one place instead of having two separate buttons (Add Button and the Apps buttons).

Ditto to Rune's comment - I have keyboard shortcuts turned off because too many times unexpected things happen.
Ditto to everyone else's comment - only power users (who don't have the problem Rune and I have) use keyboard shortcuts. The main complaint that we all have is that actions that are performed regularly and that admins work hard to have users remember to do NEED TO BE VISIBLE.

I think keyboard shortcuts should be a complement, and not the primary way of doing an action.

As others point out, many users don't know about keyboard shortcuts, or just aren't using them.

I myself, as an org admin, power user, and general Atlassian Cloud advocate has turned off keyboard shortcuts all together.
Too often I found myself thinking I had selected a text field, begun typing, and then a hundred unintended things happened.

Please prioritize actual UI buttons first and make shortcuts as a secondary.

2239430e27fb 
I think you then should find a place for them in the new side bar navigation rather than in the topmenu.
Most of our users dont even know shortcuts exist.
They need visible buttons they can click on.

keyboard shortcuts are not of any use for the majority of Jira users. Most people who use Jira probably do so to get a job done, rather than frequently and considered enough to remember shortcuts. It is kind of the same reason hiding these quick actions also doesn't work - most users need key actions front and centre.

My recommendation would be to offer 'sticky' quick action that appear 'old style' across the top rather than in the drop down. The sticky options should also be rolled out with certain actions defaulted to sticky, such as 'Attachment', 'Subtask', 'Linked Issue' and 'Weblink'. Then its only when a Jira instance starts adding all sort of extra apps to the menu that the admin needs to consider what should be sticky and what shouldn't.

Hey Everyone, 

Thank you for your feedback. 

We have moved to the dropdown menu for scalability and performance reasons. 
We are exploring solutions to the feedback on this ticket.

One idea is to introduce keyboard shortcuts to our most popular objects. 
We welcome feedback on this possible change to address the feedback on this ticket.

Please develop this ASAP! Wild that you would just push out a UI change without any proactive messaging to admins/users, and then at the same time provide zero methods to opt-out! It's like the product owner(s) that pushed for this change doesn't actually use Jira! Freakin' wild.

I agree with others that this can add substantial time to workflows and obfuscate tools unnecessarily.

Ideally, it would be possible to toggle whether these are present to all users as individual buttons and for each user to be able to toggle their own layout as well. Something similar to how users can pin their own selection of fields in the sidebar.

Please make this configurable by the user, so we can prioritise the actions we use most, and have the rest under " Add more..." or similar.

Also, as a side-note, the blinking border around the "+ Add" button is extremely irritating when I'm typing in the card. Having a blinking UI elements in a productivity application should have been outlawed decades ago!

This is a great idea. We're in an environment with more apps than my previous company and so decluttering the menu is welcome, but I do appreciate that some companies do not have the same challenges. 

This would be helpful, as calling up the AKs in the mask is somewhat cumbersome, especially for longer descriptions. 

Please implement this instead of the recent UI change (https://community.atlassian.com/t5/Jira-articles/Quick-Add-Menu-is-Getting-Decluttered/ba-p/2840225/)

This functionality is required for a smooth and efficient UX, following this unpopular change (anecdotally, lots of those with early access to this, including me, had the change reverted because it made the experience worse - now it seems we're stuck with it).

For our usage, we mostly just link issues, which is now an extra click away.

I'm not sure I understand how this helps anyone in any org without giving the option of admins to toggle this or pin specific quick actions to the issue viewer.  I'm sure I'll be echoing others here but there needs to be a compromise for this.

Suggestions:

• Create separate view options
• Add the ability to pin specific actions by a project admin

Thank you to whomever submitted this request as having commonly used buttons hidden under another button is really annoying. I'm surprised there was enough customer demand for that to have it actually implemented but based on community feedback it appears that there are a large number of customers who are not happy with the change.

Hi 252f72cf7deb and ef3f01a4b196! After discussing this with our product manager 2239430e27fb , it was clarified that using the "old" style for quick actions is not something that would be in the plans, but being able to pin actions covers the same need and gives even more flexibility, so we have updated the feature request to now focus on that suggestion.

I'm sorry, but he new design is not better for everyone.  Our screens are not cluttered and now have a huge whitespace at the top and requires extra clicks by our users.

Also, implementing a change like this should ALWAYS have controls to enable and disable. When the BETA version of this was released, I had it immediately reverted and so did many other clients. 

rchiquete , do you know if there is a feature request yet for what ef3f01a4b196 described? I'm also looking for improvements to the new "apps" and "not apps" quick actions structure. 

Hi ef3f01a4b196, just to clarify, feature requests are created from different sources. One of the sources is from requests from customers, like in this case where the request was directly to be able to use the previous style. Due to this, some feature requests may be very specific in what they ask at the start, and over time, with feedback and additions from comments like yours, our product managers can make an informed decision about what resonates the most with our customers.

I agree with ef3f01a4b196. We don't need a way to enable/disable this update. We need to include the ability to pin actions that are used more often. This would allow for the best of both worlds.

Given configuration is a hallmark of Jira, is strange that the "Quick Actions" team did not implement either of these before forcing this change on everyone.

• different view options (as described)
• admin feature to pin frequently used actions (make them always visible)

Hope they take quick action to remedy the oversight