My power users also made heavy use of the 'dot' menu for editing specific field values. We're just learning that only system fields (like Status or Story Points) can be edited using the actions menu in Jira Cloud, and it's both a bummer and a productivity killer for many of our heaviest users.

+1 to making the 'dot'/cmd+K menu allow users to edit a specific field (custom or otherwise).

Taking away vital functionality like this is completely inexplicable and the lack of intelligible explanations for this are troubling to say the least. As an admin, I rely on "gg" to do half of my work. The new search is not only more difficult to access but much less robust and less helpful for admins. 

Thanks 1f215302a950! Some of those fields are ones I would edit regularly with that functionality.

I really don't understand why they're being so selective with the fields you can edit. Why can't they just open it up to all available fields on a card's screen/view? I would understand if maybe certain custom fields weren't available as MVP, but still would expect that to be on their roadmap. Atlassian took away a super simple editing tool. And why they couldn't just stick with what worked, ".", instead of Ctrl+K is interesting, but I'm willing to make the switch if they can make it consistent. 

e8cdf5b4096a I tried to include a screen shot but I guess i don't have permissions to do so.

Copy / paste of the feature notes (still rolling out on July 9, 2024)

Feature: Edit issue details using just your keyboard

We’ve expanded the functionality of the command palette so it’s even easier to edit your issues.

You can now use your keyboard to edit the following fields on an issue:

• Sprint

• Labels

• Due date

• Fix versions

• Priority

• Story points

• Components

To edit issue details with the command palette.

1. Open the issue you want to edit.

1. Open the command palette by selecting command + K if you’re a Mac user, or Ctrl + K if you’re a Windows user.

1. Select the issue action you want to perform.

1f215302a950 - for those of us without access to Admin, can you provide high level info on what the new feature is?

I see a new similar feature rolling out.   It might be a step in the right direction, it hasn't reached my instance so i can't test.

https://admin.atlassian.com/o/238ab99b-a93d-1c48-j2j0-3625d4bd03d0/changelog/22gBmqgyTgrBLppH8odfSv

I've given up on this functionality but it does take me back to a time when J I R A was lean and ergonomic. The power is still there under the hood but a lot of what made it quick and delightful is harder to find.

The . shortcut was SO GOOD and to have had it and then lost it is just tough as a customer. Also the responses to this story just sitting here for years with little engagement is not great feeling for me.

             ,dPYb,                                            
             IP'`Yb                                            
             I8  8I                                            
             I8  8'                                            
 gg,gggg,    I8 dP   ,ggg,     ,gggg,gg    ,g,      ,ggg,      
 I8P"  "Yb   I8dP   i8" "8i   dP"  "Y8I   ,8'8,    i8" "8i     
 I8'    ,8i  I8P    I8, ,8I  i8'    ,8I  ,8'  Yb   I8, ,8I     
,I8 _  ,d8' ,d8b,_  `YbadP' ,d8,   ,d8b,,8'_   8)  `YbadP'     
 PI8 YY88888P8P'"Y88888P"Y888P"Y8888P"`Y8P' "YY8P8P888P"Y888    
 I8                                                            
 I8                                                            
 I8                                                            
 I8                                                            
 I8                                                            
 I8                                                            

                                                        I8                  I8                
                                                        I8                  I8               
                         gg                          88888888            88888888            
                         ""                             I8                  I8               
     ,gggggg,   ,ggg,    gg    ,ggg,,ggg,     ,g,       I8      ,gggg,gg    I8     ,ggg,     
     dP""""8I  i8" "8i   88   ,8" "8P" "8,   ,8'8,      I8     dP"  "Y8I    I8    i8" "8i    
    ,8'    8I  I8, ,8I   88   I8   8I   8I  ,8'  Yb    ,I8,   i8'    ,8I   ,I8,   I8, ,8I    
   ,dP     Y8, `YbadP' _,88,_,dP   8I   Yb,,8'_   8)  ,d88b, ,d8,   ,d8b, ,d88b,  `YbadP'    
   8P      `Y8888P"Y8888P""Y88P'   8I   `Y8P' "YY8P8P 8P""Y8 P"Y8888P"`Y8 8P""Y8 888P"Y888   

                                                                                             
                                                                                             
     I8    ,dPYb,                                 ,dPYb,         8I               8I                 I8           
     I8    IP'`Yb                                 IP'`Yb         8I               8I                 I8           
  88888888 I8  8I                                 I8  8I         8I               8I              88888888        
     I8    I8  8'                                 I8  8'         8I               8I                 I8          
     I8    I8 dPgg,    ,ggg,           ,ggggg,    I8 dP    ,gggg,8I         ,gggg,8I    ,ggggg,      I8          
     I8    I8dP" "8I  i8" "8i         dP"  "Y8ggg I8dP    dP"  "Y8I        dP"  "Y8I   dP"  "Y8ggg   I8          
    ,I8,   I8P    I8  I8, ,8I        i8'    ,8I   I8P    i8'    ,8I       i8'    ,8I  i8'    ,8I    ,I8,         
   ,d88b, ,d8     I8, `YbadP'       ,d8,   ,d8'  ,d8b,_ ,d8,   ,d8b,     ,d8,   ,d8b,,d8,   ,d8'   ,d88b,        
   8P""Y8 88P     `Y8888P"Y888      P"Y8888P"    8P'"Y88P"Y8888P"`Y8     P"Y8888P"`Y8P"Y8888P"     8P""Y8 
       

 ,dPYb,                                        I8                                                 ,dPYb,         I8  
 IP'`Yb                                        I8                                                 IP'`Yb         I8              
 I8  8I                                     88888888  gg                                          I8  8I  gg  88888888           
 I8  8'                                        I8     ""                                          I8  8'  ""     I8              
 I8 dP   gg      gg   ,ggg,,ggg,     ,gggg,    I8     gg     ,ggggg,     ,ggg,,ggg,     ,gggg,gg  I8 dP   gg     I8    gg     gg 
 I8dP    I8      8I  ,8" "8P" "8,   dP"  "Yb   I8     88    dP"  "Y8ggg ,8" "8P" "8,   dP"  "Y8I  I8dP    88     I8    I8     8I 
 I8P     I8,    ,8I  I8   8I   8I  i8'        ,I8,    88   i8'    ,8I   I8   8I   8I  i8'    ,8I  I8P     88    ,I8,   I8,   ,8I 
,d8b,_  ,d8b,  ,d8b,,dP   8I   Yb,,d8,_    _ ,d88b, _,88,_,d8,   ,d8'  ,dP   8I   Yb,,d8,   ,d8b,,d8b,_ _,88,_ ,d88b, ,d8b, ,d8I 
PI8"888 8P'"Y88P"`Y88P'   8I   `Y8P""Y8888PP 8P""Y8 8P""Y8P"Y8888P"    8P'   8I   `Y8P"Y8888P"`Y88P'"Y888P""Y8 8P""Y8 P""Y88P"888
 I8 `8,                                                                                                                     ,d8I'
 I8  `8,                                                                                                                  ,dP'8I 
 I8   8I                                                                                                                 ,8"  8I 
 I8   8I                                                                                                                 I8   8I 
 I8, ,8'                                                                                                                 `8, ,8I 
 "Y8P'                                                                                                                   `Y8P"

many thanks in advance. I know you can do it. Make a lot of us happy using JIRA. Come on. Prove us wrong

I invite all others to join me in repeating the ask via: https://www.messletters.com/en/big-text/

Be creative! Make this a crowd fun

The loss of this functionality is completely inexplicable. The individual fields are now found in one of several difficult-to-differentiate categories (Pinned, Details, More Fields), so are more difficult to actually locate on the form. And, with no keyboard shortcut to easily update such entries, productivity is taking a major hit. What used to be a quick, short sequence of keyboard shortcuts, is now forced to be: A scan of the page searching for the field in question, kicking open the category sections as needed, again looking for the particular field, and then using a pointing device to actually click on the field in order to open it for editing. Why was the prior functionality completely removed?

Note that this ticket has been open for six years, and the latest indication from Atlassian is that they are are "currently working on a new keyboard shortcut experience that will be launched in the near future" … but this was posted one year ago. Is there really any hope of this being revisited, and corrected?

I echo the sentiment of many.  Using "," was a real time saver to edit any issue field, getting access to the actions menu is not nearly as useful.

Just migrate to Jira cloud from server. Now can't quickly edit fields from "," menu - need to click on them in the interface to edit them - that's much less productive than quickly accessing them from "," menu and editing them. Please bring back quick field edit from "," menu!

Disappointed that even when I can use the dot menu to open a part of the issue I want to add data to (like Add web link or Link issue), the text field it opens isn't highlighted. I can use the dot menu to bring it up, but then have to mouse into it anyway to paste/type what I'm adding. 

I mainly used the dot-menu in Jira server for editing issue fields, I would very much like that functionality to be added in Jira cloud. The current options are of limited value.

P.s.

I suspect that if you have usage statistics for this functionality in Jira server you will find that it is mostly used for editing fields.

Just migrated from server to cloud, and my favorite shortcut "." doesn't work anymore. This is a real pain because I hate to do everything with a mouse click.

This 'dot' menu gave my instant access to the reminder-date field.

ppppppp       lll        eeeeeeeeeeee         aaaaaa           ssssssssssss    eeeeeeeeeeee
pp     pp     lll        ee                 aaaa   aaaa      ssss              ee
pp     pp     lll        eeeeee            aaaa     aaaa      ssssss           eeeeee
ppppp         lll        eeeeee           aaaa aaaaa aaaa          sssssss     eeeeee
pp            lll        ee               aaaa       aaaa            ssssss    ee     
pp            llllllll   eeeeeeeeeeee     aaaa       aaaa     sssssssssss      eeeeeeeeeeee     

                                                         reinstate this functionality

I'm with Thierry on this one – please bring back this feature. Using keyboard shortcuts is just way faster than relying on that tiny critter scurrying around on your desk.

Terribly missing this option specially to quick edit Hide when empty fields and jump to fields quickly.

 
"We are currently working on a new keyboard shortcut experience that will be launched in the near future. "

The old dot-menu (and comma-menu) were so good that i was recommending them as a model for other applications to follow!

Also, if you want to do a "new keyboard shortcut experience" then fine - but have it ready before you get rid of the old one!

We've just gone back to Cloud from On Prem (long story) and are disappointed to see that the dot shortcut is gone

I got a notification today about the "command-K" menu in Jira.  I was hoping that that would fix things, but alas, it has not.

I really miss being able to quickly go though a list of tickets and using the "." menu to do everything, assign the ticket to sprints, add labels, link to epics, etc. etc.  

For me, it's not that the pop-up menu doesn't work, it's just that the options available inside are limited from what they used to be.  Even if I can't edit custom fields from this menu, that might be acceptable, but at least let me edit ALL core fields that ship with a standard Jira project.  

I am also disappointed Jira cloud doesn't has this shortcut. 
My use case is straightforward. During grooming session I would, for example, enter a ticket and use (in Jira DC) "," shortcut to select a field for editing, would type "story" so I could edit story points and that would be it. 

This still cannot be done in Jira Cloud.

Hi Everyone,

I'm interested in getting more details about your use cases for the dot menu. Is anyone keen for a quick 30 minute chat?

Please feel free to respond here with your email address or book directly via this link: https://calendly.com/emditchfield/customer-chat 

Cheers,

Emily Ditchfield

Product Manager, Jira Software

Just migrated from Jira server to Jira cloud, I was using this feature daily. It will now be slower to do the same job as before. My team is disapointed.

https://getsupport.atlassian.com/browse/JST-835394

I'm currently teaching the Jira Administration Part 1 class and it would be great to tell students that these features work always, on all pages. Unfortunately that's not currently the case.

One more vote.  Huge loss of efficiency!

Still not working properly. After MIgration to Jira Cloud my team was really disappointed in the loss of the features.

There's so much more clicking involved in estimating story points for a number of issues.

I would love for this to work! All things that can make you faster in admin is a productivity win! 

It's *REALLY *annoying you can't always use the "gg" shortcut... Please fix this!

A bug report for implemented functionality:

Case the issue is opened from search page, the `dot` button does not have the actions from the last fix (link, attach, move, delete, etc). The URL is like 

https://company_name.atlassian.net/browse/ISSUE-1?jql=text%20~%20%22test123%22

If you specifically look at the Summary of the problem you'll find that you have not released the "high value feature" yet, you have only solved a bit of the problem.  Please bring back the shortcut for fields, as this saves an incredible amount of time for people doing triage of large products where you need to track a lot of fields.   

> Summary

> Jump to fields for editing Keyboard shortcut do not work on new Issue view ("," or "gg" or ".")

For us essentials are:

• story points
• sprint
• fix version
• affected version
• epic
• labels

@VenkateshVasudevan - thanks for the update, this is a big and welcome step. As others have mentioned however, there are still features not available (editing Story Points and other fields would be great to come next for us), and some features that would benefit from refinement (e.g. navigating to the Permissions Helper now forgets which issue you were in and requires you to have remembered and to re-enter this).

Some functions are finally working, "Link" as the first more important point.

But when you open the menu by pressing ., the dot is already in the text field and you have to erase it first.

Come on guys, have you ever tried to test the software before releasing it? Please fix it!

Just bring the functions back as it was before Jira cloud, this menu worked perfectly, we could navigate to fields like story points etc.

The dot menu only allows for taking actions on the issue.  

The dot, then comma, then now nothing, does not provide the ability to Jump to a Field!  You took away helpful functionality!

The improvement is live on JSM as well, as of today – @Pavel, @Arturs, you guys were right.

Issue actions

• Link issue
• Link Confluence page
• Add web link
• Assign to me
• Comment
• Log work
• Connect Slack channel
• Move
• Clone
• Delete

Workflow

• Applicable transitions in your workflow

Hopefully more to come soon.

Would also love to see story points and the ability to edit fields with the dot dialog menu. Used to be able to do this in the old Jira view.

My teams would love to see story points sooner than later in the dot menu.

@Andras, it is available also for us.  Probably they are rolling this out slowly as there are no official updates in the ticket. We have Jira experiments / Jira Labs enabled so maybe that is why we already see this feature.

9a164abff6b3 I saw this on our Jira instance, maybe they make it available gradually for some cloud instances?

https://snipboard.io/A8UYp5.jpg

@Pavel, where exactly is this update shared?

Still no update of any kind in Jira Service Management, dot menu is empty.

Indeed a good start. Thx.
Looking forward to the remaining ones 

More actions have come to the dot menu   Press . while viewing an issue to quickly perform issue actions, move an issue through its workflow, access admin settings, and more.  

 
Some actions like link, move, do transition to Done for example are now available, however edit of the fields like Fix Version, Label, Epic still does not work.

The good start though!

Please just bring back "." shortucts for triggering issue state transitions.

I was used to open issue, check status, test stuff etc. and then possibly change the status using only keyboard:
1. Press dot (".")
2. Type "Do..."
3. Press enter (confirm move to "Done" transition)

With the new issue view I am bound to use mouse like a caveman. 😭

almost 3y...

"Suggestion"!??

Since this is a high volume issue I beg anyone visiting here to help their fellow Atlassian users who are suffering with other incredibly difficult to swallow regressions even if you don't use Plans the same hard to imagine level of failure is occurring there. please vote on this issue as well: https://jira.atlassian.com/browse/JPOSERVER-2562

The whole pushing of the new view as default without fixing major feature regressions first is really awful. Not even talking about the general uselessness of the new view for heavy power users with lots of content in the tickets.

Have you checked how many people used this feature prior to deciding it's merely a "suggestion" and not a bug?

Also, what about clearly upfront communicating what features are still broken on the new view instead of letting the users find out by themselves which makes it only worse?

If you won't fix these issues before removing the old view entirely, which we currently still use with an auto redirecting script for, we'll definitely seriously consider us staying with Jira. Despite the APIs integrations we have with it, making it less and less useful for humans is unacceptable.

Request for all coming to this issue to vote on https://jira.atlassian.com/browse/JRACLOUD-76586. "." menu workflow is truly not complete if you still have to use the mouse to commit field changes

"Feature regression". I didn't know that was a thing until today.

I am frustrated by this feature regression and have been since the new ui was released. It is sad that the new shiny UI has been prioritized over functionality. It sounds like management is prioritizing getting new customers over keeping existing customer happy or functional.

The process on this ticket has been even worse than the bug. Information has been slow. Promises were made. Updates are not being provided, and the forced default was pushed without fixing the bug AND THE BUG HAS BEEN DISMISSED AS A SUGGESTION AND DEPRIORITIZED.

This issue goes a long way to convince me to never adopt or recommend an Atlasssian product at my job and to recommend replacing it with a competitor at every opportunity. Bugs happen and software is hard, but blindly ignoring the users who care enough to try and help you make the product better is worse than an engineering failure.

I DON'T NORMALLY SHOUT BUT I'M ABSOLUTELY ASTOUNDED THAT YOU REMOVED THIS NECESSARY FUNCTIONALITY AND YOU WON'T GIVE IT BACK TO US – AND MEANWHILE YOU'RE EXPECTING US TO PAY THE SAME $$$ FOR REDUCED FUNCTIONALITY.

AS MENTIONED IN PRIOR COMMENTS, ONE NEEDS TO MOUSE TO GET TO THE OLD VIEW (AND THUS THE FULL FUNCTIONALITY OF KEYBOARD SHORTCUTS) – AND THEN WHEN ONE LOOKS AT ANOTHER ISSUE, IT'S BACK TO THE NEW-ISSUE-VIEW AGAIN.

PLEASE RETURN MY USER TO DEFAULTING TO THE OLD VIEW UNTIL THIS FIX IS IN PLACE. I'VE ASKED FOR THAT AND WAS DENIED: https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-655303?error=login_required&error_description=Login+required&state=91552e2b-e880-448b-8aa2-17aff12e8ecd

WHEN ARE YOU FORECASTING THIS FIX TO BE ON PRODUCTION?

Please return the option to make old view the default view in this case

I would like to point out that the description mentions a workaround (namely to click through to the old issue view).  But people who prefer keyboard shortcuts do not wish to use the mouse.  But to click through to the old issue view, you have to use the mouse.

What's the point in clicking with the mouse so you can hit a key?  It requires a mouse click to avoid mouse clicks.