• 16
    • 28
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The Quick actions menu has recently been updated to show a more compact version and this opens the way for now having more space in the UI. It would be good to be able to utilize this space by being able to pin actions so that they are not collapsed under the "Add" button, and immediately accessible at all times.

      • Allowing the administrators to set some default pinned actions on a Project-issue type level, while also allowing users to pin the actions they want on an user account level would give even more flexibility.

      Original Description

      The Quick actions menu has recently been updated to show a more compact version. This style is not be optimal for all teams and scenarios, and it would be good to have a way to toggle/choose which version to use.

      For context, the old style looked like this:

      And this is how it looks now:

            [JRACLOUD-85131] Allow choosing the Quick actions style

            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.

            Jared Moore added a comment - 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.

            Sarah Vrla added a comment -

            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.

            Sarah Vrla added a comment - 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!

            Neal McConachie added a comment - 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. 

            Michele Colson added a comment - 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. 

            Susan Behrendt added a comment - This would be helpful, as calling up the AKs in the mask is somewhat cumbersome, especially for longer descriptions. 

            Rune Rasmussen added a comment - 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/ )

            James added a comment -

            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.

            James added a comment - 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

             

            Nick Walters added a comment - 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.

            Rick Westbrock added a comment - 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.

            Rene C. [Atlassian Support] added a comment - - edited 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. 

            Corey Hampton added a comment - 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. 

            Henri Seymour {Easy Agile} added a comment - 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.

            Rene C. [Atlassian Support] added a comment - 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.

            Gary Spross added a comment - 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.

            The way this issue is described right now, does not point in the right direction. You suggest turning the new layout altogether, but that would be a step backwards - why would you do that? The new design is taking the actions menu in the good direction, but is not sufficient and was released prematurely. As I'm seeing it now, the only missing thing is the ability for the admins to pin actions outside of dropdown buttons.

            That would be the best of both worlds. Not going back to the old design, which was in fact getting cluttered.

            Arkadiusz Seidel added a comment - The way this issue is described right now, does not point in the right direction. You suggest turning the new layout altogether, but that would be a step backwards - why would you do that? The new design is taking the actions menu in the good direction, but is not sufficient and was released prematurely. As I'm seeing it now, the only missing thing is the ability for the admins to pin actions outside of dropdown buttons. That would be the best of both worlds. Not going back to the old design, which was in fact getting cluttered.

            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

            Dwight Holman added a comment - 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

              2239430e27fb Ahmud Auleear
              rchiquete Rene C. [Atlassian Support]
              Votes:
              68 Vote for this issue
              Watchers:
              57 Start watching this issue

                Created:
                Updated: