Labels and <enter> key

[Tomas Løvbukten]

When adding a label to an issue, I'm used to start writing something - and when the list of suggestions comes up, I use the <down> arrow key to select the right one and hit <enter> to save it. 

The problem is that nowadays, the <enter>-key just closes the list of suggestions, and no label is added. 

The same thing happens when I enter a new label, the return key does not save it. Is this a new feature of some sort, or just a bug? If not a bug, is there a way to add labels just by using the keyboard without involving the mouse? 

[Tomas Løvbukten]

Atlassian support has confirmed the issue and closed it by creating the following bugreport:

https://jira.atlassian.com/browse/JRACLOUD-75125

[Doreen Müller]

I experience the same, using Jira cloud. It used to work fine until some time ago, maybe about 4 weeks now?

[Tomas Løvbukten]

Thanks for letting me know. You're the first person to confirm that this is an issue not just valid to us. Atlassian support has had my issue in <Atlassian investigating> mode for 7 days now, let's hope they find a solution. In the meantime - I'm using classic issue view. 

[Doreen Müller]

I don't have this problem with other lists, like inserting user names in issues. Hopefully, something will happen to your support request. 

[Tomas Løvbukten]

I've raised this issue with Atlassian Support, and wait for some response there. 

I've also noticed that we have the same issue with other selector components, like Component, Assignee, Affect Versions, Fix Version as well. So it's not just Label where I first noticed this.

[Mariana_Pryshliak_Saasjet]

Hello @Tomas Løvbukten 

I did the same a few minutes ago and I didn't notice any problems. 

This may be a bug.

[Ste Wright]

Hi @Tomas Løvbukten 

To confirm, you are:

1. Clicking on the Labels field - or pressing "L" (keyboard shortcut)
2. Searching & moving up/down the list using keyboard arrow keys 
3. Pressing Enter to add an existing label - or writing a new one and pressing Enter to add it

^ I tried this on both the "New Issue View" and "Classic View" just now and it works fine for me.

Have you tried using the keyboard shortcut? And does it happen for anyone else on your instance?

Ste

[Tomas Løvbukten]

Thanks for the reply! 

I can confirm that your list describes what I experience, both when using "L" keyboard shortcut and when clicking in the label field to edit it.

We're using JIRA software cloud and "new issue view". After your feedback here, I tested using "Classic/old issue view" - and there it worked as expected!

And after switching back to "new issue view", the label control just aborts without saving anything when using enter key. 

So to me, this looks like either a bug or some race condition feature with the new issue view. 

I get the same bug on next-gen projects and classic projects.

[Ste Wright]

Hi @Tomas Løvbukten 

Is it happening for just you? Could you ask another user on your instance to try this?

Could you also try on a different browser?

As I say, I tried this in the "New Issue View" and it works as expected, so I don't think there's a bug in the issue view overall.

It might be a setting on your instance, or a computer/browser setting?

Ste

[Tomas Løvbukten]

Thanks for the swift replies and good suggestions! Here are the results from Norway: 

• Myself and 3 other colleagues get the same results on various computers
• We get the same results in Chrome, Edge and Opera
• The same results are in a JIRA classic software project and in a next-gen project
• The label-control works as expected and saves properly 
  • when in "Create Issue popup"
  • if we switch edit issue view to "classic issue view"
• The label-control does not work as expected as it just cancels when pressing enter
  • in edit issue view (when "new issue view" is enabled)
  • the same thing happens when using "L" key or mouse / tab to get in there

Any tip on any settings that could be related, or should this be filed as a bug?

By the way, 12 points to Sweden!

[Ste Wright]

Hi @Tomas Løvbukten 

Strange!

I would raise this with Atlassian Support as a next step, as it's inconsistent between your instance and ours. They're best placed to investigate this further first!

To contact support, visit: https://support.atlassian.com/

Ste