You need to make changes to the time tracking feature in Jira.

Thetime trackingfeature in Jira Cloud allows logging work, tracking estimates, and managing time-related settings. The configuration that can be controlled globally across all projects isthe default tracking time unit, unless users explicitly specify one(Option C), as this is set in the global time tracking settings.

Explanation of the Correct Answer (Option C):

Thedefault tracking time unit(e.g., hours, days) is configured globally in Jira Cloud’s time tracking settings and applies to all projects unless users specify a different unit when logging time or setting estimates. This setting determines how time is displayed and entered by default across the system.

Exact Extract from Documentation:

Configure time tracking in Jira Cloud

Global time tracking settings apply to all projects and include:

Default time unit: Sets the default unit for time tracking (e.g., hours, days).To configure:

Go toSettings > Issues > Time tracking.

Set theDefault unit for time tracking(e.g., Hour).Impact: The default unit is used across all projects unless users explicitly specify another unit (e.g., 2d for days).Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Configure time tracking in Jira Cloud")

Why This Fits: Thedefault tracking time unitis a global setting that applies to all projects, making Option C the correct answer.

Why Other Options Are Incorrect:

The ability to log work on issues for specific groups (Option A):

The ability to log work is controlled by theWork On Issuespermission in each project’s permission scheme, not globally. Permissions are project-specific, even if projects share a scheme, and cannot be set globally for specific groups across all projects.

Extract from Documentation:

TheWork On Issuespermission is set in project permission schemes, not globally.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

The ability to edit or delete their own or other users’ worklogs for specific users (Option B):

Permissions to edit or delete worklogs (e.g.,Edit Own Worklogs,Edit All Worklogs,Delete Own Worklogs,Delete All Worklogs) are also set in project permission schemes, not globally. These are project-specific settings.

Extract from Documentation:

Worklog permissions (Edit Own Worklogs,Delete All Worklogs) are configured in project permission schemes, not globally.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

The availability of time tracking fields on standard versus sub-task issue types (Option D):

The availability of time tracking fields (e.g., Original Estimate, Remaining Estimate) is controlled byfield configurationsorscreens, which are project-specific or issue type-specific. There is no global setting to differentiate timetracking fields between standard and sub-task issue types.

Extract from Documentation:

Time tracking fields are managed by field configurations and screens, not global settings. Their availability depends on project or issue type configurations.

(Source: Atlassian Support Documentation, "Configure field settings")

The requirement of an original estimate when creating issues (Option E):

Requiring anOriginal Estimateis controlled byfield configurations(making the field required) orworkflow validators(enforcing a value during transitions). These are project-specific or issue type-specific, not global settings.

Extract from Documentation:

Requiring fields likeOriginal Estimateis set in field configurations or workflow validators, not globally.

(Source: Atlassian Support Documentation, "Configure field settings")

Additional Notes:

Configuring global time tracking settings requiresJira administratorprivileges and is done inSettings > Issues > Time tracking.

Other global time tracking settings include the format (e.g., hours per day, days per week) and whether time tracking is enabled.

Project-specific settings (e.g., permissions, field requirements) override global defaults for specific use cases.