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 Leaders.
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 Leaders.
I use the "dot menu" for one thing, and one thing only: to change the ticket status. The command palette doesn't support this, I have to look at the screen to select the option. With the dot menu, I could just type whatever I wanted and press enter and I knew it'd work. No need to select on the screen, much faster and less prone to error.
I LOVE the dot menu. It has been the top feature I introduce to jira users everywhere. ctrl-k is not the same I would say, at least as an admin. Much harder to get the correct choice (custom fields in one that I will not get directly). And I do not think that ctrl+k works in the issue navigator wich has been such an amazing feature. As an admin I think gg is sooo much better since I only get the admin stuff.
Another key-shortcut? Jira already mess things up with shortcuts that accidently remove me from tickets and other crap. Please have clickable options, for all things.
@Yousef Abusamak Please don't proceed with this change. It is a strict degradation in user experience and your responses admit as much while only making vague promises to "consider" fixing some of the introduced regressions in "the future". While we all know Atlassian never actually gets to any of the things on its roadmap if they come from user complaints - just visit the Jira issue tracker to see that.
@Yatesh Not sure if my user-tagging of you will work, but I'm happy to elaborate...
My 2nd Shortcut: "m" to begin a comment; Cmd+v pastes the contents of my clipboard into the new comment. My new comment is the evidence that the work for my ticket is complete. For this project, it's effectively our User-Acceptance Testing.
My 3rd Shortcut: "." to invoke the Dot menu; "lv" is the most unique part of the string `Resolved` when compared to the other ticket Statuses available to this project's workflow.
Maybe that will be useful for you! Generally I'm a big fan of Jira, and I'm also a big fan of navigating Jira via the keyboard. I just learned recently that the Escape key is a shortcut for closing an active ticket modal; I love that.
@Preston Dockery Nooo.. You should not have mentioned the Esc key! Now they will do anything in their power to replace that with the very useful "del" key...
why not add all options that dot menu had into the command pallete? now I have to execute two actions in the command pallete to the stauts of the case. I would prefer in that case to simply click on the status and change it, which makes it obsolete.
Please get rid of the debounce (delay to update matches after keypress). I'm doing more waiting than anything else when I try to use this menu!
It effectively kills any advantage that you had with the dot-menu. At this rate it is even faster to use the mouse (especially given that top-level entries like status changes are now nested and require multiple interactions).
As long as Ctrl-K doesn't provide issue actions for the selected issue in List View, it's not equivalent to the Dot menu. Thus, disabling the Dot menu for the sake of Ctrl-K menu introduces a regression in the UX.
Even the simple action of adding a comment to the selected issue becomes complicated. You have to either:
open the issue,
click the 3 dot (if you find it. it may be on the hidden on right side if you have many columns) and then type
Switch to detailed view (particularly not a friendly one. Doesn't even have a resizable splitter)
Please fix that issue. The command pallete should support issue actions when a single issue is selected in 'list mode'
I get that the new command palette is more powerful, but, please, leave the dot shortcut alone. As power users, we got used to the shortcut. I get that cmd+k or ctrl+k is shared among a lot of other apps nowadays (shame it's not the dot), and that's great that you introduce that shortcut too, but that doesn't mean you have to get rid of the . shortcut.
Do you have metrics like "." is rarely used so you feel fine butchering it off? I feel discriminated as a . user now. #dotMatters
Please enhance the feature but keep the shortcut(s) as much as possible.
#resistTheChange #ifItAintBrokeDontFixIt (but seriously, keep the dot, pretty please!)
Going from 1 keyboard press to 2 keyboard presses is more work for your users
Because I'm an Admin who uses a Mac laptop but whose company will only give me a Windows keyboard, I now have to remember two different keyboard shortcuts, depending on whether I'm working on my laptop-only or with my laptop plugged into my full desk setup
Across most applications, CTRL+K is the standard keyboard shortcut for adding hyperlinks to text - why make it mean something different for only this Jira functionality?
"the dot menu is constrained by its code, making it difficult to update" doesn't seem like a good reason to force this change on all users - just improve the code so your users can keep the easy, consistent functionality they've used for years!
Will the additional Actions (out-of-issue context actions) be available by the time you remove the dot/gg options? You stated August 19th 2024. I expect to be able to CTRL+K and reach things like the Audit Log, or Shared Filters the same as I do today with dot menu.
Can you please not remove the dot menu until AFTER you have added in the features that are currently lacking? As an admin, I use the dot menu to quickly navigate to specific settings pages for our installed Apps -- with multiple Apps that have many settings pages (like ScriptRunner), it is a huge pain to scroll down on the Manage Apps page to find the one I want.
The dot menu was one of my favorite features in Jira, very quick to change issue states.
For example, to approve an issue:
Press "."
Start typing the desired state transition ("Ap" is sufficient to drill down to the desired option)
Press Return
With the "Ctrl+K" menu:
Press "Ctrl+K"
Type "D"
Press Return
Start typing the state transition ("Ap" is sufficient to drill down to one option)
Press Return
How did this pass a UX review?
And why not add issue state transitions to the top search level to restore the old, fast workflow. Right now when I start writing "Ap" it suggests "Go to timeline" and "Switch to dark theme", which makes no sense.
It seems like a good idea that it's not quite there yet
I'm trying to get used to it, but honestly, for me, it doesn't make a lot of sense to deprecate a very good feature for one that's not quite there yet.
It seems like a promising way forward and I believe you all put a lot of effort into making this tool which will probably enable you to create an even better user experience for us, but I wouldn't deprecate the old one just yet. I would, just like some features you have, let the user decide what they want.
Faster and easier to use the mouse in some cases
Also, linking issues is easier to do with a mouse than with this new command palette which for me, defeats the purpose of having a command palette 🤷♂️
There are more menus reachable from the Settings menu that can't be accessed using the palette. It would be great that it would cover every menu. To mention one: Script Console.
I assume there is a chance that any app related menu is not reachable as of today.
72 comments