Understanding the default focus in the Create Issue screen


Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

When a new issue is created from the agent view, in some cases, the default focus when opening up the create issue screen is not on the first expected field. It takes a few tab movements to get to that field. The purpose of this article is to explain why this happens.

This affects Jira Service Management projects

Cause

Some inconsistent behavior has been noticed with the default focus in the Create Issue screen. For example, when the Reporter field or the Raise a request on behalf of field which is a drop down select list is the first field on the Create Issue screen (after the issue type and request type fields), the user has to press tab key several times to end up with the focus on the Summary field or the first text field.

On the other hand, when a text field (like the Summary field) is the first field, the default cursor/focus is shown in the Summary field immediately when the screen is opened or when the project is selected.

This auto-focus issue can occur whenever any field is placed before a text field.

A video of this behavior is attached below:

Solution

This is an intentional behavior where the functionality has been put in place to not have the default focus set when the first field on the create issue screen is not a text field like summary, description, etc. This has been done to avoid the unnecessary dropdown fields getting opened up when the user opens the screen. This is the reason why the Reporter field or the Raise a request on behalf of is not getting focused in such instances.

This functionality will not be changed. We also unfortunately do not have a way to disable it just for a specific instance.


Last modified on Jan 20, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.