Summary

      Since the new UI when viewing an issue and you use the shortcut key (.) to edit the Summary or any other field, the field is highlighted but not focused to type in. You must click in the field first before typing. This was not the case on the previous UI and it defeats the purpose of using keyboard shortcuts.

      Environment

      Steps to Reproduce

      Steps to reproduce (keyboard only):
      1) Navigate to any issue
      2) Press .
      3) Start typing summary
      4) Select Summary from overlay window
      5) Summary field is highlighted, but not focused for typing

      Expected Results

      The Summary field should be focused for typing without using the mouse. 

      Actual Results

      The field is highlighted but not focused for keyboard entry

      Notes

      Workaround

      No existing workarounds. Fields can still be edited once clicked.

            [JRACLOUD-69028] Keyboard shortcut to edit issue fields does not focus on field after new interface

            Closing this one as duplicated of JRACLOUD-71827 and JRACLOUD-69301, which are now In Progress

            Gabriele Franck added a comment - Closing this one as duplicated of JRACLOUD-71827 and JRACLOUD-69301 , which are now In Progress

            Also posted this comment on JRACLOUD-69876 but it seems like it might be needed here too:

            I would like to add in my experience that the ability to edit an issue via keyboard shortcuts is imperative for our user base. Two reasons: 1) speed (having to click, type, click to make each field update is really a flow killer) and 2) it is nice to make all edits in a single action to avoid spamming people with issue update notifications.

            Barrett Cope added a comment - Also posted this comment on JRACLOUD-69876 but it seems like it might be needed here too: I would like to add in my experience that the ability to edit an issue via keyboard shortcuts is imperative for our user base. Two reasons: 1) speed (having to click, type, click to make each field update is really a flow killer) and 2) it is nice to make all edits in a single action to avoid spamming people with issue update notifications.

            this is a huge issue! It was working for a bit but the error seems to have popped up again. 

            Andreas Cruz added a comment - this is a huge issue! It was working for a bit but the error seems to have popped up again. 

            Trevor Morehead added a comment - related: https://jira.atlassian.com/browse/JRACLOUD-69061  

            This would be a valuable change for my development team. 

            Deleted Account (Inactive) added a comment - This would be a valuable change for my development team. 

            This does seem like a significant break in how the shortcut functionality should work.

            Can we get an increase in priority for this?

            Trevor Morehead added a comment - This does seem like a significant break in how the shortcut functionality should work. Can we get an increase in priority for this?

            Please increase priority.   This completely breaks the value of having keyboard shortcuts.  For me this is a significant workflow issue preventing quicker editing. 

            This is NOT a workaround.  Please simply acknowledge the feature is broken.  There are far fewer steps for the user to just click the field in the 1st place.

            Administrator added a comment - Please increase priority.   This completely breaks the value of having keyboard shortcuts.  For me this is a significant workflow issue preventing quicker editing.  This is NOT a workaround.  Please simply acknowledge the feature is broken.  There are far fewer steps for the user to just click the field in the 1st place.

            The problem is the same for every "text" field. Labels, severity, sprint, epic link, fix versions, and so on.

            Deleted Account (Inactive) added a comment - The problem is the same for every "text" field. Labels, severity, sprint, epic link, fix versions, and so on.

              vvasudevan@atlassian.com Venkatesh Vasudevan (Inactive)
              dmark@atlassian.com Danny (Inactive)
              Votes:
              25 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: