Issue Summary

Currently, when users change the status of an issue, the workflow status dropdown shows only a limited number of statuses at once. In projects with a large number of statuses and/or transitions available from a given status, users must scroll extensively to find the correct status.

There is no configuration option at the site, project, workflow, or UI level that allows admins or users to:

• Increase the default height of the status dropdown

• Show more statuses at once without scrolling

• Expand the dropdown to a larger view

This creates usability and productivity issues in environments with complex workflows or many statuses.

Steps to Reproduce

1. In Jira Cloud, create or use a project with a workflow that has a large number of statuses and transitions (e.g., 20–40+ valid next statuses from a given status).

1. Open any issue that uses this workflow.

1. Click on the issue’s Status field to open the workflow status dropdown.

1. Attempt to select a status that appears near the end of the list.

Expected Results

Provide a way for users or admins to increase the number of visible statuses in the dropdown. For example, one or more of the following:

• A larger default dropdown height when many statuses are present.

• An option to “expand” or “show more” statuses (e.g., a taller or full-height panel).

• A per-user UI preference or accessibility option to increase list/dropdown heights.

• Smarter adaptive sizing where the dropdown uses more vertical screen space when available.

The goal is to reduce the amount of scrolling and make it easier and faster to find the intended status, especially in complex workflows.

Actual Results

• The status dropdown has a relatively small viewable area.

• Only a limited number of statuses are visible at one time.

• Users must scroll a long way through the dropdown to reach the desired status, especially when many statuses are available from the current status.

Workaround

There are no direct UI or configuration workarounds to increase the dropdown height. The only partial mitigations are workflow design changes, such as:

• Splitting very long workflows into smaller, more focused workflows per issue type/request type.

• Reducing the number of rarely used statuses.

• Avoiding “All → All” transitions to limit the number of valid next statuses from each status.

These workarounds do not solve the underlying UI limitation for customers who need richer workflows.