Issue Summary

Currently, in Jira Cloud, the board's Estimation Statistic (e.g., Story Points) dictates the estimation badge shown on the Backlog view. This badge is universally rendered for every issue type in the backlog list. If a board uses Story Points for parent issues but tracks subtasks in hours, the subtasks render an empty - badge for Story Points. This creates visual clutter and confusion for users. Administrators need the ability to toggle or hide these estimation badges on a per-issue-type basis (specifically for subtasks) so that only relevant issue types display the badge.

Steps to Reproduce

1. Create a Company-managed project with a Scrum board.

1. Navigate to Board settings > Estimation and set the Estimation Statistic to "Story Points".

1. Create a Story and add a Subtask to it. Do not add Story Points to the Subtask (as it will be tracked in hours).

1. Navigate to the Backlog view and expand the parent Story to reveal the Subtask.

Expected Results

Board administrators have a configuration option to hide the estimation badge for specific issue types (like subtasks) so that empty badges do not clutter the UI.

Actual Results

The estimation badge is hardcoded to display on all issue rows. The subtask displays a - badge indicating the field is empty, which cannot be disabled or hidden.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.