how to disable keyboard shortcuts in Jira

[Magdalena Migas]

Dear Community, 

Could you please advise how to limit, turn off shortcuts in Jira ? 

My team is pretty annoyed by them and they are constantly making the same error in Jira by changing assignee which is strongly impacting my work. 

Thank you in advance, 

BR

[Matt Tse]

Hi @Magdalena Migas,

Thanks for the question! My name’s Matt and I’m one of the product managers in Jira Cloud. My team picked this problem up and have just started to roll out a feature that will allow users to enable/disable shortcuts at a per-user level.

See the attached screenshot of what this will look like. We were constrained by time so we decided to put it into the keyboard shortcut (Shift + ?) dialog for now. We believe this will address the problem and in the future, we will consider adding it inside the user profile page.

As of this afternoon, it will be available to 5% of Jira Cloud customers and we aim to get this rolled out to 100% in early August.

Kind regards,
Matt

[Bill Sheboy]

Thanks for the response and the feature, @Matt Tse !

Who goes through the old suggestions and defects to mark them as resolved when a feature like this gets addressed?

[Matt Tse]

Hey @William Sheboy,

Great question. The answer is that it really depends. Each team works on different problem spaces and it really falls to the team to decide what areas are relevant to their focus area. We have innovation time that we can spend working on areas that are not roadmapped. In this case, we saw an opportunity with this keyboard shortcut feature and decided it was worth the investment and time.

Hope that helps answer your question.

Cheers,

Matt

[Bill Sheboy]

Hi @Matt Tse 

Thanks for the information, and that wasn't what I meant, so I'll try explaining another way.

As a product person, you know backlogs go stale over time...and there are several ways to manage that, such as best-by dates, truncation, periodic refinement, "no backlog", etc.  I was asking about the older items in the backlog which are resolved by a feature or defect fix, and the resulting backlog clean-up.  A healthy backlog helps people when searching to learn if there are existing issues around a concern, so they don't add a duplicate.  I was asking how the clean-up happens.

Thanks again,

Bill

[Bill Sheboy]

Removing duplicate reply due to some site/posting latency issue.

[Matt Tse]

Thanks for the clarification. Apologies for misunderstanding the question.

I'm assuming by "Backlog", you're referring to the public issues raised on jira.atlassian.com. If a team does address an issue that's been raised publicly, they will often search through the issues and update its respective workflow to whatever is most appropriate (e.g., In progress, Future Consideration, Not Being Considered, Closed, Gathering interest, Waiting for release).

That being said, there are plenty of public issues that are not in any team's active backlog because of the shift in our priorities/focus areas. In many cases, the respective PMs who last worked in the respective areas will provide some sort of closure or remark that states what the team is doing about said issue.

Does that answer your question? 

Cheers,

Matt

[Bill Sheboy]

Yes, that answers the question.  Thanks, @Matt Tse 

[Bill Sheboy]

Hi @Magdalena Migas 

I do not believe there is a way to disable them with out-of-the-box JIRA.  There are several suggestions to add this feature, which you can review and vote for:

https://jira.atlassian.com/issues/?jql=project%20IN%20(JRACLOUD%2C%20JSWCLOUD)%20AND%20resolution%20%3D%20Unresolved%20AND%20summary%20~%20disable%20AND%20summary%20~%20shortcut%20ORDER%20BY%20Key

Best regards,

Bill