ACP-120 Updated Exam Dumps [2025] Practice Valid Exam Dumps Question [Q33-Q55]

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. RenamingDoneto Finishedupdates 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 like Resolution. 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 administrator privileges.
* 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.
:
Atlassian Support Documentation:Manage resolutions in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Manage dashboards in Jira Cloud

Reference: https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

Restoring a Jira Cloud instance with a backup involves importing data, users, and media from thebackup file.
Valid options include importing data, merging or overwriting users, and importing media. However, importing apps(Option B) is not a valid option, as apps are not included in Jira Cloud backups and must be reinstalled separately.
* Explanation of the Correct Answer (Option B):
* Jira Cloud backups include issues, configurations, users, and media (e.g., attachments) but do not include installed apps or their data. Restoring a backup does not involve importing apps, as apps must be reinstalled from the Atlassian Marketplace and configured separately.
* Exact Extract from Documentation:
Restore Jira Cloud from a backup
A Jira Cloud backup includes:
* Issues and their history.
* Configurations (e.g., workflows, schemes).
* Users and groups.
* Media (e.g., attachments).When restoring:
* Import data: Restore issues and configurations.
* Merge with existing Cloud users: Add users from the backup without overwriting existing users.
* Overwrite existing Cloud users: Replace existing users with those from the backup.
* Import media: Restore attachments and other media.Note: Apps and their data are not included in backups. Reinstall apps from the Atlassian Marketplace after restoring.(Source:
Atlassian Support Documentation, “Restore your Jira Cloud site from a backup”)
* Why This Fits:Importing appsis not a valid option for restoring a Jira Cloud backup, as apps are excluded from backups, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Import data (Option A):
* Importing data is a valid option, as it restores issues, configurations, and other Jira data from the backup.
* Extract from Documentation:
Import data to restore issues, projects, and configurations from a Jira Cloud backup.
(Source: Atlassian Support Documentation, “Restore your Jira Cloud site from a backup”)
* Merge with existing Cloud users (Option C):
* Merging users is a valid option, allowing users from the backup to be added to the existing Cloud instance without overwriting current users.
* Extract from Documentation:
ChooseMerge with existing Cloud usersto add users from the backup while preserving existing user accounts.
(Source: Atlassian Support Documentation, “Restore your Jira Cloud site from a backup”)
* Overwrite existing Cloud users (Option D):
* Overwriting users is a valid option, replacing existing users with those from the backup.
* Extract from Documentation:
ChooseOverwrite existing Cloud usersto replace current users with those from the backup.
(Source: Atlassian Support Documentation, “Restore your Jira Cloud site from a backup”)
* Import media (Option E):
* Importing media is a valid option, restoring attachments and other media files from the backup.
* Extract from Documentation:
Import media to restore attachments and other files included in the backup.
(Source: Atlassian Support Documentation, “Restore your Jira Cloud site from a backup”)
* Additional Notes:
* Restoring a Jira Cloud backup requiresJira administratorororganization adminprivileges and is done viaSettings > System > Restore.
* After restoring, apps must be reinstalled, and their data may need to be reimported if the app supports it.
:
Atlassian Support Documentation:Restore your Jira Cloud site from a backup Atlassian Support Documentation:Manage apps in Jira Cloud

Adding a new issue type to a company-managed project requires updating configurations that map issue types to various settings (e.g., screens, workflows, fields). The configuration item that isdefinitely not impactedis theissue security scheme(Option C), as it controls issue visibility and is not directly tied to issue types.
* Explanation of the Correct Answer (Option C):
* Anissue security schemedefines security levels that restrict which users can view issues in a project, based on criteria like users, groups, or roles. It is applied at the project level and is not specific to issue types. Adding a new issue type does not require changes to the issue security scheme, as security levels apply to all issues in the project regardless of their type.
* Exact Extract from Documentation:
Configure issue security schemes
Issue security schemes define security levels to control who can view issues in a project.
Impact of issue types:
* Security levels are applied to all issues in a project, regardless of issue type.
* Adding a new issue type does not affect the issue security scheme.To check:
* Go toProject settings > Issue security.
* Review the security levels and their criteria.Note: Issue security is independent of issue type configurations.(Source: Atlassian Support Documentation, “Configure issue security schemes”)
* Why This Fits: Theissue security schemeis not impacted by adding a new issue type, as it operates at the project level and does not depend on issue type configurations, making Option C the correct answer.
* Why Other Options Are Incorrect:
* Issue layout (Option A):
* Theissue layoutdefines which fields are displayed or hidden in the issue view for each issue type. Adding a new issue type may require configuring a new issue layout to specify field visibility for that type, impacting this configuration.
* Extract from Documentation:
Issue layouts are configured per issue type inProject settings > Issue layout. Adding a new issue type may require a new layout configuration.
(Source: Atlassian Support Documentation, “Configure issue layouts in Jira Cloud”)
* Issue type screen scheme (Option B):
* Theissue type screen schememaps screens to issue types for operations (Create, Edit, View). Adding a new issue type requires assigning a screen to it in the scheme, impacting this configuration.
* Extract from Documentation:
Adding a new issue type requires updating the issue type screen scheme to assign screens for the new type.
(Source: Atlassian Support Documentation, “Configure screen schemes in Jira Cloud”)
* Workflow scheme (Option D):
* Theworkflow schememaps workflows to issue types. Adding a new issue type requires assigning a workflow to it in the scheme, impacting this configuration.
* Extract from Documentation:
Adding a new issue type requires updating the workflow scheme to assign a workflow for the new type.
(Source: Atlassian Support Documentation, “Configure workflow schemes”)
* Field configuration scheme (Option E):
* Thefield configuration schememaps field configurations to issue types, defining field behavior (required, optional, hidden). Adding a new issue type may require assigning a field configuration to it, impacting this configuration.
* Extract from Documentation:
Adding a new issue type may require updating the field configuration scheme to assign a configuration for the new type.
(Source: Atlassian Support Documentation, “Configure field settings”)
* Additional Notes:
* Steps to add a new issue type:
* Add the issue type to the project’s issue type scheme inProject settings > Issue types.
* Update theissue type screen scheme,workflow scheme, andfield configuration schemeto include the new issue type.
* Configure theissue layoutfor the new issue type if needed.
* These changes requireJira administratorprivileges for schemes andproject adminprivileges for issue layout.
* Theissue security schemeremains unaffected, as it applies to all issues in the project.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Configure screen schemes in Jira Cloud
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Configure field settings

In team-managed projects, workflows are simplified and configured withinProject settings > Workflow.
Users (typically project admins) can add rules to transitions, such as clearing fields, restricting transitions, or setting field values. However, team-managed workflows do not support complex automation-like rules, such as automatically reopening Sub-tasks when a Story is reopened, as this requires interacting with related issues (Sub-tasks), which is not supported out-of-box in team-managed workflow rules.
* Explanation of the Correct Answer (Option B):
* The rule toreopen Sub-tasks when reopening Storiesrequires a workflow rule to detect the transition of a Story to an open status and then automatically transition its Sub-tasks to an open status. Team-managed workflows do not support rules that affect related issues (e.g., Sub-tasks) during a transition. This functionality requires Jira automation or a company-managed project workflow with custom post functions, which are not available in team-managed projects.
* Exact Extract from Documentation:
Configure workflows in team-managed projects
Team-managed projects use simplified workflows that allow adding rules to transitions, such as:
* Restricting transitions to specific users or roles.
* Setting or clearing field values (e.g., Assignee, Description).
* Requiring fields to be filled.Rules are limited to the issue being transitioned and cannot affect related issues (e.g., Sub-tasks, Epics). To automate actions on related issues, use Jira automation rules.Note: Team-managed workflows are project-specific and edited inProject settings > Workflow.(Source: Atlassian Support Documentation, “Configure workflows in team-managed projects”)
* Why This Fits: The rule to reopen Sub-tasks requires interacting with related issues (Sub-tasks), which is beyond the capabilities of team-managed workflow rules, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Rule to clear the Assignee when closing (Option A):
* Team-managed workflows support rules to clear fields during a transition. A rule can be added to the transition to theClosedstatus to clear theAssigneefield.
* Extract from Documentation:
You can add a rule to a transition to clear a field, such as Assignee, when moving to a status like Closed.
(Source: Atlassian Support Documentation, “Configure workflows in team-managed projects”)
* Rule to ensure only Peter can approve Stories (Option C):
* Team-managed workflows allow restricting transitions to specific users or roles. A rule can be added to the transition to anApprovedstatus to allow only Peter to perform it.
* Extract from Documentation:
Add a rule to restrict a transition to a specific user (e.g., Peter) or role, ensuring only they can move issues to a status like Approved.
(Source: Atlassian Support Documentation, “Configure workflows in team-managed projects”)
* Rule to clear the Description when reopening (Option D):
* Team-managed workflows support clearing fields during transitions. A rule can be added to the transition to anOpenstatus to clear theDescriptionfield.
* Extract from Documentation:
Rules can clear fields like Description during a transition, such as when reopening an issue.
(Source: Atlassian Support Documentation, “Configure workflows in team-managed projects”)
* Rule to ensure only the Reporter can close bugs (Option E):
* Team-managed workflows allow restricting transitions to specific users, including the Reporter. A rule can be added to the transition to theClosedstatus for bugs to allow only the Reporter to perform it.
* Extract from Documentation:
Restrict a transition to the Reporter to ensure only they can move issues to a status like Closed.
(Source: Atlassian Support Documentation, “Configure workflows in team-managed projects”)
* Additional Notes:
* Team-managed workflows are designed for simplicity, with rules limited to the issue being transitioned. Complex logic, such as affecting Sub-tasks (Option B), requires Jira automation rules, which are separate from workflow rules.
* Peter, as a project admin in a team-managed project, can edit the workflow inProject settings > Workflow.
:
Atlassian Support Documentation:Configure workflows in team-managed projects Atlassian Support Documentation:Automate your Jira Cloud instance

The question involves managing versions in a company-managed project in Jira Software Cloud. Maia wants to move all issues from version 1.1 to version 1.2 and remove version 1.1 as an available option in theFix Versionsfield. The two operations that meet both requirements areArchiveandMerge.
* Explanation of the Correct Answers:
* Archive (Option B):
* Archiving a version removes it from theFix Versionsfield as an available option for new issues, while preserving the version’s association with existing issues. Additionally, archiving allows you to move issues to another version (e.g., version 1.2) during the process, meeting both requirements.
* Exact Extract from Documentation:
Archive a version
Archiving a version removes it from the list of available versions in fields like Fix Versions, so it can’t be selected for new issues. You can also move issues to another version during the archiving process.
To archive a version:
* Go to your project’sReleasespage.
* Find the version (e.g., version 1.1) and selectArchive.
* Optionally, choose to move issues to another version (e.g., version 1.2).Archived versions are still visible in reports and issue details but are no longer selectable in fields.Note: You need project admin permissions to archive versions.(Source:
Atlassian Support Documentation, “Manage versions in company-managed projects”)
* Why This Fits: Archiving version 1.1 removes it from the Fix Versions field, preventing it from being selected for new issues, and allows Maia to move all issues to version 1.2 during the archiving process, fulfilling both requirements.
* Merge (Option D):
* Merging a version moves all issues from one version (e.g., version 1.1) to another (e.g., version 1.2) and deletes the source version, effectively removing it from the Fix Versions field. This meets both requirements, as it reassigns issues and eliminates version 1.1 as an available option.
* Exact Extract from Documentation:
Merge versions
Merging versions allows you to combine two versions by moving all issues from one version to another. The source version is deleted after the merge.
To merge versions:
* Go to your project’sReleasespage.
* Find the version to merge (e.g., version 1.1) and selectMerge.
* Choose the target version (e.g., version 1.2) to move issues to.After merging, the source version (version 1.1) is removed from the Fix Versions field and is no longer available for selection.Note: Merging is permanent and cannot be undone, so ensure the target version is correct.(Source: Atlassian Support Documentation, “Manage versions in company-managed projects”)
* Why This Fits: Merging version 1.1 into version 1.2 moves all issues to version 1.2 and deletes version 1.1, ensuring it is no longer an option in the Fix Versions field, thus meeting both requirements.
* Why Other Options Are Incorrect:
* Delete (Option A):
* Deleting a version removes it from the Fix Versions field, but it also removes the version from all issues associated with it without reassigning them to another version. This does not meet the requirement to move issues to version 1.2.
* Extract from Documentation:
Delete a version
Deleting a version removes it from the project and clears it from the Fix Versions field of all associated issues. Issues are not reassigned to another version automatically.
Note: Use caution, as this action cannot be undone, and issues lose their version association.
(Source: Atlassian Support Documentation, “Manage versions in company-managed projects”)
* Build and release (Option C):
* Building and releasing a version marks it as complete and moves unresolved issues to another version, but it does not remove the version from the Fix Versions field. Released versions remain selectable unless archived or deleted.
* Extract from Documentation:
Release a version
Releasing a version marks it as complete and optionally moves unresolved issues to another version. The released version remains available in the Fix Versions field unless archived.
(Source: Atlassian Support Documentation, “Manage versions in company-managed projects”)
* Additional Notes:
* BothArchiveandMergeare suitable, but they have different implications:
* Archiving preserves version 1.1 in reports and issue histories, making it ideal if historical data needs to be retained.
* Merging permanently deletes version 1.1, which may be preferred if the version is no longer relevant.
* The operations require project admin permissions in a company-managed project, and the Releasespage is accessed viaProject Settings > Releases.
:
Atlassian Support Documentation:Manage versions in company-managed projects Atlassian Support Documentation:Configure releases and versions

TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including projects, issues, configurations, and attachments. However,deleted issues(Option C) cannot be imported, as they are not included in standard Jira Cloud backups or export data.
* Explanation of the Correct Answer (Option C):
* Deleted issuesare permanently removed from Jira Cloud and are not included in backups or export files created for migration. TheImport Jira Cloudfeature only imports data that exists in the source site’s backup, which excludes issues that have been deleted.
* Exact Extract from Documentation:
Import Jira Cloud data
TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including:
* Projects (company-managed and team-managed).
* Issues, comments, and attachments.
* Configurations (e.g., custom fields, workflows, automation rules).Limitations:
* Deleted issues are not included in backups or exports and cannot be imported.To import:
* Create a backup from the source site inSettings > System > Backup manager.
* UseSettings > System > Import Jira Cloudon the target site.Note: Requires Jira administrator permissions and may involve Atlassian support for full migrations.(Source:
Atlassian Support Documentation, “Import data to Jira Cloud”)
* Why This Fits:Deleted issuesare not part of the data exported from the source site, making them impossible to import, so Option C is the correct answer.
* Why Other Options Are Incorrect:
* Automation rules (Option A):
* Automation rulesare included in Jira Cloud backups and can be imported to the target site using theImport Jira Cloudfeature, provided they are compatible with the target site’s configuration.
* Extract from Documentation:
Automation rules are included in Jira Cloud backups and can be imported, though some rules may require reconfiguration if dependencies (e.g., custom fields) differ.
(Source: Atlassian Support Documentation, “Import data to Jira Cloud”)
* Custom fields (Option B):
* Custom fieldsare part of the configuration data in a Jira Cloud backup and are imported to the target site. Their contexts and options are preserved during migration.
* Extract from Documentation:
Custom fields, including their configurations and contexts, are included in backups and imported to the target site.
(Source: Atlassian Support Documentation, “Import data to Jira Cloud”)
* Team-managed projects (Option D):
* Team-managed projectsare fully supported in Jira Cloud backups and can be imported to the target site, including their issues, configurations, and settings.
* Extract from Documentation:
Both company-managed and team-managed projects are included in Jira Cloud backups and can be imported to another site.
(Source: Atlassian Support Documentation, “Import data to Jira Cloud”)
* Attachments (Option E):
* Attachments(media files) are included in Jira Cloud backups and can be imported to the target site, provided the backup includes media data.
* Extract from Documentation:
Attachments are included in Jira Cloud backups and imported to the target site if media import is enabled.
(Source: Atlassian Support Documentation, “Import data to Jira Cloud”)
* Additional Notes:
* TheImport Jira Cloudfeature is accessed viaSettings > System > Import Jira Cloudand typically requiresJira administratorprivileges, with possible Atlassian support for full migrations.
* Deleted issues are permanently removed and cannot be recovered unless a backup from before deletion is available, but even then, they are not part of standard exports.
* Other data (e.g., automation rules, custom fields) may require post-import reconfiguration if there are incompatibilities between sites.
:
Atlassian Support Documentation:Import data to Jira Cloud
Atlassian Support Documentation:Back up Jira Cloud data

The requirement involves automating an action during a workflow transition (copying a comment entered on a transition screen to the work log description when closing issues). As correctly noted, this type of automation is typically handled by aworkflow post function, which executes actions after a transition is completed. However, the provided options do not include “workflow post function.” Among the options, Workflow condition(Option D) is the closest, as it points to the general area of workflow configuration where post functions are also managed, despite being technically inaccurate since conditions and post functions serve different purposes. Let’s analyze this in detail.
* Explanation of the Correct Approach (Workflow Post Function):
* Aworkflow post functionis the appropriate mechanism to copy the comment entered on the transition screen to the work log description during theClose Issuetransition. Post functions are executed automatically after a transition completes, and they can manipulate issue data, such as copying field values. However, Jira’s out-of-the-box post functions (e.g.,Copy Value From Other Field) may not directly support copying a transition screen comment to a work log description, as the comment field on a transition screen is transient and not stored as a standard issuefield until the transition is complete. This may require a custom post function or a third-party app (e.g., ScriptRunner) to script the behavior.
* Alternatively, aJira automation rulecould achieve this by triggering on theIssue Transitioned event (to the Closed status) and copying the latest comment to the work log description, but automation rules are configured separately and not part of the workflow editor.
* Exact Extract from Documentation:
Configure workflow post functions
Post functions are executed after a transition is completed and can perform actions like updating fields or copying data.
To configure:
* Go toSettings > Issues > Workflows.
* Edit the workflow and select theClose Issuetransition.
* Add a post function (e.g.,Copy Value From Other Fieldor a scripted post function via an app).Note: Copying a transition screen comment to a work log description may require a custom script or third-party app, as standard post functions do not directly support this.
(Source: Atlassian Support Documentation, “Configure advanced work item workflows”)
* Why This Fits the Requirement: A post function on theClose Issuetransition can automate the copying of the comment to the work log description, aligning with the requirement for an action during a workflow transition.
* Analysis of the Options and Selection of Option D:
* The options provided do not include “workflow post function,” which is the precise configuration area. However, let’s evaluate each option:
* Field configuration (Option A):
* Field configurationscontrol whether fields are required, optional, or hidden for specific issue types. They do not handle automation or copying data between fields during transitions.
* Extract from Documentation:
Field configurations manage field behavior (required, hidden), not field value copying or automation.
(Source: Atlassian Support Documentation, “Configure field settings”)
* Global time tracking settings (Option B):
* Global time tracking settingsconfigure time tracking formats, permissions, and defaults (e.g., enabling time logging, setting time units). They do not control copying data between fields like comments and work log descriptions.
* Extract from Documentation:
Global time tracking settings manage time tracking behavior, not field interactions or automation.
(Source: Atlassian Support Documentation, “Configure time tracking in Jira Cloud”)
* Issue layout (Option C):
* Issue layoutsdetermine field visibility and arrangement in the issue view (e.g., which fields are shown or hidden). They do not manage automation or data copying during transitions.
* Extract from Documentation:
Issue layouts control field display in the issue view, not field value copying or automation.
(Source: Atlassian Support Documentation, “Configure issue layouts in Jira Cloud”)
* Workflow condition (Option D):
* Workflow conditionsrestrict who can perform a transition (e.g., only users in a specific group). They do not execute actions like copyingdata between fields, which is the role of apost function. However, both conditions and post functions are configured within the same workflow editor (under the transition settings), making Workflow conditionthe closest option to the general area of workflow configuration where post functions reside. The question’s options may reflect a terminology error, intending “workflow post function” but listing “workflow condition” instead. Given the context of a workflow transition action, Option D is the most plausible choice despite the inaccuracy.
* Extract from Documentation:
Conditions restrict transition access, while post functions perform actions like updating fields. Both are configured in the workflow editor under the transition settings.
(Source: Atlassian Support Documentation, “Configure advanced work item workflows”)
* Global permissions (Option E):
* Global permissionscontrol system-wide actions (e.g., Administer Jira, Work On Issues). They do not manage field interactions or automation during transitions.
* Extract from Documentation:
Global permissions manage system access, not field automation or workflow actions.
(Source: Atlassian Support Documentation, “Manage global permissions”)
* Why Option D is Selected: WhileWorkflow conditionis technically incorrect (as conditions do not copy data), it points to the workflow configuration area where the correct solution-apost function-is implemented. In the absence of a “workflow post function” option, Option D is the closest match, likely due to a wording error in the question. The user’s analysis aligns with this interpretation, recognizing that the solution lies within the workflow editor, specifically with post functions.
* Additional Notes:
* Steps to Configure a Post Function:
* Go toSettings > Issues > Workflows(requires Jira administrator privileges).
* Edit the workflow used by the project and select theClose Issuetransition.
* Add a post function to copy the transition screen comment to the work log description (this may require a custom script or third-party app like ScriptRunner, as standard post functions do not directly support this).
* Alternative with Automation Rule:
* Go toProject settings > Automation(orSettings > System > Automation rulesfor global rules).
* Create a rule with the triggerIssue Transitioned(to Closed status).
* Add a condition to check for a new comment (if needed).
* Add an action to edit the work log and copy the latest comment to the work log description (may require scripting or app support).
* The question’s options suggest a possible oversight in not including “workflow post function.” However, interpretingWorkflow conditionas a reference to the broader workflow configuration area (where post functions are managed) makes it the most reasonable choice.
:
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Automate your Jira Cloud instance
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Configure time tracking in Jira Cloud
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Manage global permissions

Reference: https://confluence.atlassian.com/adminjiraserver/logging-and-profiling-938847671.html
https://confluence.atlassian.com/crowd/logging-and-profiling-24248601.html

In Jira Software Cloud, theAssigneefield for a new issue can be set toAutomatic, in which case Jira determines the assignee based on the project’sDefault Assigneesetting and any component-specificDefault Assigneesettings. The issue in the ENG project has all four components selected (Activation, Bin, Cart, Database), and the Assignee is left asAutomatic. The issue will be assigned to theProject Lead(Option E) due to the rules for handling multiple components with conflicting default assignees.
* Explanation of the Correct Answer (Option E):
* Project Default Assignee: The project ENG has itsDefault Assigneeset to theProject Lead, meaning that if no component-specific assignee is determined, the issue will be assigned to the Project Lead.
* Component Default Assignees:
* Activation: Default Assignee isComponent lead(User 1).
* Bin: Default Assignee isProject default(Project Lead).
* Cart: Default Assignee isComponent lead(User 3).
* Database: Default Assignee isUnassigned.
* Automatic Assignment Logic with Multiple Components: When an issue has multiple components selected, Jira evaluates theDefault Assigneefor each component:
* If all components have the same default assignee, that user is assigned.
* If components have different default assignees (or some are unassigned), Jira falls back to the project’sDefault Assignee(Project Lead in this case).
* In this scenario:
* Activationassigns to User 1.
* Binassigns to the Project Lead (via project default).
* Cartassigns to User 3.
* Databaseassigns to Unassigned.
* Since the components have conflicting default assignees (User 1, Project Lead, User 3, Unassigned), Jira cannot resolve to a single assignee and uses the project’sDefault Assignee, which is theProject Lead.
* Exact Extract from Documentation:
Configure default assignees
TheDefault Assigneefor a project or component determines who is assigned to new issues when theAssignee field is set toAutomatic.
Multiple components:
* If an issue has multiple components with different default assignees, Jira assigns the issue to the project’sDefault Assignee.To configure:
* Go toProject settings > Componentsto set component default assignees.
* Go toProject settings > Detailsto set the project’sDefault Assignee.Note: The project’s Default Assigneeis used when component assignees conflict.(Source: Atlassian Support Documentation, “Manage project settings in Jira Cloud”)
* Why This Fits: With conflicting default assignees across the four components, Jira assigns the issue to the project’sDefault Assignee, which is theProject Lead, making Option E the correct answer.
* Why Other Options Are Incorrect:
* User 1 (Option A):
* User 1 is the default assignee for theActivationcomponent (as the Component lead).
However, with multiple components selected and different assignees (User 1, Project Lead, User 3, Unassigned), Jira falls back to the project’sDefault Assignee(Project Lead), not User 1.
* Extract from Documentation:
If multiple components have different default assignees, the project’sDefault Assigneeis used, not a component-specific assignee.
(Source: Atlassian Support Documentation, “Manage project settings in Jira Cloud”)
* User 2 (Option B):
* User 2 is the Component lead forBin, but the default assignee forBinis set toProject default(Project Lead), not the Component lead. Even if it were User 2, the conflicting assignees across components would result in the Project Lead being assigned.
* Extract from Documentation:
TheProject defaultsetting for a component assigns issues to the project’sDefault Assignee, not the Component lead.
(Source: Atlassian Support Documentation, “Manage components in Jira Cloud”)
* User 3 (Option C):
* User 3 is the default assignee for theCartcomponent (as the Component lead). However, the conflicting assignees across components (User 1, Project Lead, User 3, Unassigned) result in the Project Lead being assigned, not User 3.
* Extract from Documentation:
Conflicting component assignees result in the project’sDefault Assigneebeing used.
(Source: Atlassian Support Documentation, “Manage project settings in Jira Cloud”)
* User 4 (Option D):
* User 4 is the Component lead forDatabase, but the default assignee forDatabaseis Unassigned, not User 4. Even if it were User 4, the conflicting assignees would result in the Project Lead being assigned.
* Extract from Documentation:
TheUnassigneddefault assignee for a component does not override the project’sDefault Assigneein conflicts.
(Source: Atlassian Support Documentation, “Manage components in Jira Cloud”)
* Unassigned (Option F):
* While theDatabasecomponent has a default assignee ofUnassigned, the presence of other components with different assignees (User 1, Project Lead, User 3) creates a conflict, and Jira assigns the issue to the Project Lead, notUnassigned.
* Extract from Documentation:
Unassignedas a default assignee is overridden by the project’sDefault Assigneein cases of conflict.
(Source: Atlassian Support Documentation, “Manage project settings in Jira Cloud”)
* Additional Notes:
* TheDefault Assigneefor the project is set inProject settings > Details, and component-specific default assignees are set inProject settings > Components.
* The user creating the issue must have theAssign Issuespermission, and the Project Lead must have theAssignable Userpermission to be assigned.
* If only one component were selected (e.g., Activation), the issue would be assigned to User 1, but selecting all four components triggers the conflict resolution to the Project Lead.
:
Atlassian Support Documentation:Manage project settings in Jira Cloud
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud

The users need a field namedType of Bugto capture attributes about bugs, with the ability to manage the options themselves. The field should be a custom field (to allow naming itType of Bug) and support a predefined list of options that users can manage. TheCustom field of type Select List (single choice)(Option D) meets these needs, as it provides a dropdown list with manageable options for a single selection.
* Explanation of the Correct Answer (Option D):
* ASelect List (single choice)custom field allows users to choose one option from a predefined list (e.g., “UI Bug,” “Backend Bug”). As a custom field, it can be namedType of Bug, and project admins or Jira admins can manage the options (add, edit, or remove) in the field’s configuration.
This field type is ideal for categorizing bugs with a single attribute, and the manageable options meet the requirement for users to control the list.
* Exact Extract from Documentation:
Create a custom field
TheSelect List (single choice)field type provides a dropdown menu where users can select one option from a predefined list.
To create:
* Go toSettings > Issues > Custom fields.
* Create a new field and selectSelect List (single choice).
* Name the field (e.g., Type of Bug) and define options.
* Add the field to the project’s screens.Note: Admins can manage the options (add, edit, remove) in the field’s configuration.(Source: Atlassian Support Documentation, “Manage custom fields in Jira Cloud”)
* Why This Fits: TheSelect List (single choice)custom field allows naming the fieldType of Bug, provides a single-selection dropdown, and lets users manage the options, perfectly meeting the requirements.
* Why Other Options Are Incorrect:
* Custom field of type Select List (multiple choices) (Option A):
* ASelect List (multiple choices)custom field allows users to select multiple options from a predefined list. While it could be namedType of Bugand have manageable options, the requirement implies capturing a single attribute per bug (e.g., one type), making single- choice more appropriate than multiple-choice.
* Extract from Documentation:
TheSelect List (multiple choices)field allows multiple selections. UseSelect List (single choice)for single- value categorization.
(Source: Atlassian Support Documentation, “Manage custom fields in Jira Cloud”)
* Custom field of type Labels (Option B):
* ALabelscustom field allows users to enter free-text tags, which are not predefined and can lead to inconsistent values (e.g., “UI Bug,” “UIBug”). The requirement for users to manage options suggests a controlled list, not free-text entry, making this unsuitable.
* Extract from Documentation:
TheLabelsfield type allows free-text tags. For a predefined list, useSelect List (single choice)orSelect List (multiple choices).
(Source: Atlassian Support Documentation, “Manage custom fields in Jira Cloud”)
* Labels system field (Option C):
* TheLabelssystem field is a global field that allows free-text tags, similar to a custom Labels field. It cannot be renamed toType of Bug, and its options are not predefined or manageable in the same way as a select list. This does not meet the naming or option management requirements.
* Extract from Documentation:
TheLabelssystem field cannot be renamed and allows free-text tags. Custom fields likeSelect Listare needed for specific names and controlled options.
(Source: Atlassian Support Documentation, “Manage fields in Jira Cloud”)
* Additional Notes:
* Steps to configure:
* Create aSelect List (single choice)custom field namedType of BuginSettings > Issues > Custom fields.
* Define the options (e.g., “UI Bug,” “Backend Bug”).
* Add the field to the project’s screens (Project settings > Screens).
* Grant users permission to manage options (typically requiresJira adminorproject admin privileges).
* Configuring the custom field requiresJira administratorprivileges, but project admins can manage options if granted access.
* The field should be added to the issue layout for visibility in the issue view.
:
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Manage fields in Jira Cloud