ATLASSIAN ACP-120 - Jira Administration for Cloud

The changes toUser Default Settingsaffect the default behavior for new filters, dashboards, and issue watching. The two statements that are definitely true areonly newly created dashboards will reflect the new default setting(Option A) andonly newly created saved filters will reflect the new default setting(Option C), as these settings apply to new creations only.

Explanation of the Correct Answers:

Only newly created dashboards will reflect the new default setting (Option A):

Changing theDefault sharing for filters and dashboardstoPublicin User Default Settings sets the default sharing option for newly created dashboards toPublic. Existing dashboards retain their original sharing settings (e.g., Private, Group) and are not affected by the change. Only dashboards created after the setting is updated will default toPublic.

Exact Extract from Documentation:

Manage user default settings

TheDefault sharing for filters and dashboardssetting determines the default sharing option for new filters and dashboards.

To configure:

Go toSettings > System > User default settings.

SetDefault sharingtoPublic,Private, or another option.Impact:

Only newly created filters and dashboards use the new default setting.

Existing filters and dashboards retain their original sharing settings.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

Why This Fits: The change toPublicsharing applies only to newly created dashboards, making Option A definitely true.

Only newly created saved filters will reflect the new default setting (Option C):

Similarly, theDefault sharingsetting affects the default sharing option for newly created saved filters. Filters created after the change will default toPublic, but existing filters keep their original sharing settings (e.g., Private, Group).

Exact Extract from Documentation:

Manage user default settings

Changing theDefault sharing for filters and dashboardstoPublicapplies to new filters and dashboards only.

Impact:

Existing saved filters are not updated to the new default sharing setting.

New filters created after the change will default toPublic.(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

Why This Fits: The change toPublicsharing applies only to newly created saved filters, making Option C definitely true.

Why Other Options Are Incorrect:

Saved filters using the old default setting will reflect the new default setting (Option B):

Existing saved filters do not automatically update to the new default sharing setting (Public). They retain their original sharing configuration (e.g., Private, Group) set at creation, so this statement is false.

Extract from Documentation:

Existing filters and dashboards are unaffected by changes to theDefault sharingsetting. Only new creations use the updated default.

(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

All users will become watchers of issues they have created in the past (Option D):

SettingAutowatch own issuestoYesenables autowatching for issues createdafterthe setting is changed. It does not retroactively add users as watchers to issues they created in the past. For past issues, users must be manually added as watchers or an automation rule must be created, so this statement is not definitely true.

Extract from Documentation:

TheAutowatch own issuessetting applies to issues created after the setting is enabled. It does not affect previously created issues.

(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

Additional Notes:

ConfiguringUser Default SettingsrequiresJira administratorprivileges and is done inSettings > System > User default settings.

Users can override the default sharing setting when creating filters or dashboards (e.g., choosing Private instead of Public).

To retroactively apply autowatching to past issues, a bulk operation or automation rule would be needed, but this is not automatic.

Renaming a value in theResolutionfield (fromDonetoFinished) changes its display name globally in Jira Software Cloud. This can impact configurations or features that reference the resolution value by name, particularly in JQL queries. The element most likely to need updating issaved filters(Option B), as they often use JQL queries that include resolution values.

Explanation of the Correct Answer (Option B):

Saved filtersoften use JQL queries that reference resolution values (e.g., resolution = Done). If theResolutionfield value is renamed fromDonetoFinished, any filters using resolution = Done will no longer match issues with the renamed resolution (Finished), as the old value is no longer valid. These filters must be updated to use resolution = Finished to continue returning the correct issues.

Exact Extract from Documentation:

Manage resolutions in Jira Cloud

Resolutions are global values used in theResolutionfield to indicate an issue’s resolution state.

Impact of renaming a resolution:

JQL queries in filters, boards, or gadgets referencing the resolution name (e.g., resolution = Done) will no longer match issues if the value is renamed (e.g., to Finished).To update:

Go toIssues > Manage filters.

Edit filters to use the new resolution name (e.g., resolution = Finished).Note: Renaming a resolution affects all projects and requires updating JQL-based configurations.(Source: Atlassian Support Documentation, "Manage resolutions in Jira Cloud")

Why This Fits: Renaming a resolution value impactssaved filtersthat use JQL queries referencing the old value, requiring updates to maintain functionality, making Option B the correct answer.

Why Other Options Are Incorrect:

Workflow post functions (Option A):

Workflow post functionscan set theResolutionfield (e.g.,Set Issue ResolutiontoDone). These post functions typically use the resolution’s internal ID, not its display name, so renamingDonetoFinisheddoes not require changes to post functions.

Extract from Documentation:

Post functions reference resolution IDs, not names. Renaming a resolution does not affect workflow configurations.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Issue detail view (Option C):

Theissue detail viewdisplays theResolutionfield value as configured. RenamingDonetoFinishedupdates the display automatically without requiring manual changes to the issue detail view or its configuration (e.g.,issue layout).

Extract from Documentation:

The issue detail view reflects the current resolution name automatically. No changes are needed after renaming a resolution.

(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")

Issue Statistics gadgets (Option D):

Issue Statistics gadgets(e.g., on dashboards) can display data based on fields likeResolution. While gadgets may reference resolution values in their configuration, they typically use resolution IDs or dynamically update to reflect the renamed value. The impact is less direct than with saved filters, which rely on explicit JQL queries.

Extract from Documentation:

Gadgets like Issue Statistics use field values or IDs. Renaming a resolution may not require gadget updates unless JQL queries are explicitly used.

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

Issues in team-managed projects (Option E):

Resolutionsare global and apply to both company-managed and team-managed projects. RenamingDonetoFinishedupdates the value for all issues, including those in team-managed projects, without requiring changes to the issues themselves. The change is reflected automatically.

Extract from Documentation:

Resolutions are global and apply to all projects. Renaming a resolution updates its display for all issues without requiring issue-level changes.

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

Additional Notes:

Renaming a resolution is done inSettings > Issues > Resolutionsand requiresJira administratorprivileges.

Other JQL-based features (e.g., automation rules, boards) may also be impacted if they reference the resolution name, butsaved filtersare the most commonly affected.

To minimize impacts, use resolution IDs in JQL queries (e.g., resolution = 10000), though this is less common.