[May 17, 2026] ACP-120 Exam Dumps PDF Updated Dump from NewPassLeader Guaranteed Success
Pass Your ATLASSIAN Exam with ACP-120 Exam Dumps
ATLASSIAN ACP-120 (Jira Cloud Administrator) Exam is a certification exam designed to validate the skills and knowledge of professionals who are responsible for managing and administering Jira Cloud applications. Jira is a popular project management tool used by many businesses to track and manage their projects. The ACP-120 exam is designed to test your understanding of Jira Cloud administration, including user management, project management, and system administration.
NEW QUESTION # 24
Currently, all users in your instance can see all issues in the BRAVO company-managed project. You received these new requirements:
* Some BRAVO issues should only be visible to managers.
* Some BRAVO issues should only be visible to supervisors.
* The remaining BRAVO issues should remain visible to all users.Identify two elements that must be configured. (Choose two.)
- A. Global permissions
- B. Browse Projects permission
- C. Administer Projects permission
- D. Set Issue Security permission
- E. Issue security scheme
Answer: D,E
Explanation:
To meet the requirements of restricting visibility of some BRAVO issues to managers, others to supervisors, and keeping the remaining issues visible to all users, you need to configure anissue security schemeto define security levels and theSet Issue Securitypermission to allow users to apply these levels. These two elements are critical for implementing issue-level security in a company-managed project.
* Explanation of the Correct Answers:
* Issue security scheme (Option A):
* Anissue security schemedefines security levels that restrict who can view issues based on criteria such as users, groups, or roles. To meet the requirements, you need to create at least three security levels: one for managers, one for supervisors, and one (or none, for default visibility) for all users. The scheme is then applied to the BRAVO project to enforce these visibility rules.
* Exact Extract from Documentation:
Configure issue security schemes
Issue security schemes define security levels to restrict who can view issues. Each level specifies users, groups, or roles (e.g., managers, supervisors) who can see issues assigned to that level.
To create a scheme:
* Go toSettings > Issues > Issue security schemes.
* Create a new scheme and add security levels (e.g., "Managers Only," "Supervisors Only," "All Users").
* Assign the scheme to a project inProject settings > Issue security.Note: Security levels override theBrowse Projectspermission for restricted issues.(Source:
Atlassian Support Documentation, "Configure issue security schemes")
* Why This Fits: The issue security scheme is necessary to create security levels that restrict visibility to managers, supervisors, or all users, addressing all three requirements.
* Set Issue Security permission (Option B):
* TheSet Issue Securitypermission allows users to select a security level for an issue (via the Security Levelfield). Without this permission, users cannot assign issues to the "Managers Only" or "Supervisors Only" security levels,which is necessary to implement the restricted visibility requirements. This permission must be granted to appropriate users (e.g., project admins or specific roles) in the project's permission scheme.
* Exact Extract from Documentation:
Set Issue Security permission
TheSet Issue Securitypermission allows users to set or change the security level of an issue, determining who can view it. This permission is granted via the project's permission scheme.
To configure:
* Go toProject settings > Permissions.
* Add users, groups, or roles (e.g., Administrators) to theSet Issue Securitypermission.
Note: Without this permission, users cannot assign issues to specific security levels, even if a scheme is configured.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: TheSet Issue Securitypermission is required to enable users to apply the security levels defined in the issue security scheme, ensuring that issues can be restricted to managers or supervisors as needed.
* Why Other Options Are Incorrect:
* Global permissions (Option C):
* Global permissions (e.g.,Administer Jira,Create Projects) control system-wide actions, not project-specific visibility. Issue visibility is managed by project-level permissions and security schemes, not global permissions.
* Extract from Documentation:
Global permissions control system-wide actions, such as administering Jira or sharing filters. Issue visibility is managed by project permissions and issue security schemes.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Browse Projects permission (Option D):
* TheBrowse Projectspermission allows users to view issues in a project. While all users currently have this permission (since they can see all BRAVO issues), modifying it does not address the need to restrict specific issues to managers or supervisors. Issue security schemes overrideBrowse Projectsfor restricted issues.
* Extract from Documentation:
TheBrowse Projectspermission allows users to view issues in a project, but issue security levels can further restrict visibility for specific issues.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Administer Projects permission (Option E):
* TheAdminister Projectspermission allows users to manage project settings, such as components or permission schemes. While it may be needed to configure the issue security scheme or permissions, it is not directly required to meet the visibility requirements.
* Extract from Documentation:
TheAdminister Projectspermission allows managing project settings but is not required to set issue security levels or view restricted issues.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* To implement the requirements, create an issue security scheme with three levels:
* "Managers Only" (e.g., restricted to a "Managers" group).
* "Supervisors Only" (e.g., restricted to a "Supervisors" group).
* "All Users" (or no security level, allowingBrowse Projectsto apply).
* Assign the scheme to the BRAVO project and grant theSet Issue Securitypermission to users who need to assign these levels (e.g., project admins).
* The configuration requires Jira administrator privileges to create the scheme, but project admins can manage security levels within the project.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage global permissions
NEW QUESTION # 25
Your marketing group is using Jira to track media print advertisements. They would like to track TV and radio commercials as well.
The same team handles all three formats, but each format requires a unique workflow. The team would like to keep everything on the same dashboard, and they will also be using the same permissions, notifications and screens.
Without using third-party apps, how should you configure Jira to meet these requirements?
- A. Copy the existing permissions and notification schemes, and associate them with new projects for TV and Radio.
- B. Create a sub-component hierarchy.
- C. Clone the existing project and key for TV and Radio.
- D. Use issue types of Print, Radio and TV in the existing project.
- E. Add TV and Radio into the existing project as components.
- F. Create two new projects for TV and Radio.
Answer: F
NEW QUESTION # 26
ALPHA team handles alerts in the ALPHA project in alpha.atlassian.net. They often view and comment on bugs in the BETA project on beta.atlassian.net. The team can link ALPHA issues to other ALPHA issues but not to BETA issues. What needs to be configured?
- A. Application access
- B. Approved domains
- C. Global permissions
- D. Application links
Answer: D
Explanation:
The ALPHA team can view and comment on bugs in the BETA project (beta.atlassian.net) but cannot link ALPHA issues (alpha.atlassian.net) to BETA issues. This indicates a cross-site interaction issue, specifically with issue linking between two Jira Cloud sites. The solution is to configureapplication links(Option A) to enable linking between the ALPHA and BETA projects across the two sites.
* Explanation of the Correct Answer (Option A):
* Application linksallow Jira Cloud sites to communicate with each other, enabling features like issue linking between projects on different sites (e.g., alpha.atlassian.net and beta.atlassian.net).
Without an application link between the two sites, users cannot create links from ALPHA issues to BETA issues, even if they have access to view and comment on BETA issues. Configuring an application link between the two sites will enable cross-site issue linking.
* Exact Extract from Documentation:
Configure application links in Jira Cloud
Application links connect Jira Cloud sites or other Atlassian products, enabling features like cross-site issue linking.
To create an application link:
* Go toSettings > Products > Application links.
* Enter the URL of the target site (e.g., beta.atlassian.net).
* Follow the prompts to authenticate and configure the link.Impact:
* Allows linking issues between projects on different Jira Cloud sites.
* Requires permissions to view issues in the target project.Note: Requires Jira administrator permissions on both sites.(Source: Atlassian Support Documentation, "Configure application links in Jira Cloud")
* Why This Fits: The inability to link ALPHA issues to BETA issues is due to the lack of an application link between alpha.atlassian.net and beta.atlassian.net. Configuring an application link resolves this, making Option A the correct answer.
* Why Other Options Are Incorrect:
* Global permissions (Option B):
* Global permissions(e.g., Administer Jira, Browse Users) control system-wide actions within a single Jira site. They do not govern cross-site interactions like issue linking between two separate Jira Cloud sites.
* Extract from Documentation:
Global permissions manage actions within a single Jira site, not cross-site features like issue linking.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Application access (Option C):
* Application accessrefers to granting users access to specific Atlassian products (e.g., Jira Software, Confluence) within an organization. The ALPHA team can already view and comment on BETA issues, indicating they have access to beta.atlassian.net. Application access does not control issue linking between sites.
* Extract from Documentation:
Application access grants users product access but does not enable cross-site features like issuelinking.
(Source: Atlassian Support Documentation, "Manage product access")
* Approved domains (Option D):
* Approved domainsare used to manage cross-site authentication and security for Atlassian organizations, ensuring users from approved domains can access linked sites. While this might be relevant for user authentication, the team's ability to view and comment on BETA issues suggests authentication is not the issue. The specific problem is issue linking, which requires an application link.
* Extract from Documentation:
Approved domains manage cross-site authentication, not specific features like issue linking. Use application links for cross-site interactions.
(Source: Atlassian Support Documentation, "Manage approved domains")
* Additional Notes:
* Steps to configure:
* On alpha.atlassian.net, go toSettings > Products > Application links.
* Add a link to beta.atlassian.net and authenticate as needed.
* Repeat on beta.atlassian.net to link to alpha.atlassian.net (bidirectional link).
* Configuring application links requiresJira administratorprivileges on both sites.
* Ensure the ALPHA team has permissions to create links (Link Issuespermission) in the ALPHA project and view issues in the BETA project.
:
Atlassian Support Documentation:Configure application links in Jira Cloud Atlassian Support Documentation:Manage global permissions Atlassian Support Documentation:Manage product access Atlassian Support Documentation:Manage approved domains
NEW QUESTION # 27
Which configurations do Not have any impact on email notifications sent to users
- A. Workflow post functions
- B. Version Configurations
- C. Premission Schemes
- D. Custom Events
Answer: B
NEW QUESTION # 28
From which three sources can the Jira import wizard import data? (Choose three.)
- A. Bitbucket
- B. JSON
- C. Trello
- D. CSV
- E. GitHub
- F. Microsoft Excel
Answer: B,C,D
Explanation:
The Jira import wizard in Jira Software Cloud allows administrators to import data from various external sources to create or update issues, projects, and other entities. The supported sources includeTrello,JSON, and CSV, making these the correct choices.
* Explanation of the Correct Answers:
* Trello (Option B):
* The Jira import wizard supports importing data from Trello boards, including cards, lists, and users, into Jira projects. This is useful for migrating Trello projects to Jira.
* Exact Extract from Documentation:
Import data from Trello
The Jira import wizard allows you to import Trello boards into Jira Cloud. You can import cards as issues, lists as statuses, and map Trello users to Jira users.
To import:
* Go toSettings > System > External System Import.
* SelectTrelloand authenticate with your Trello account.
* Follow the wizard to map data and import.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Why This Fits: Trello is a supported source for the Jira import wizard, making it a correct choice.
* JSON (Option E):
* The Jira import wizard supports importing data from a JSON file, which can include issues, projects, and configurations. This is useful for advanced users or migrations from other systems that can export JSON.
* Exact Extract from Documentation:
Import data from JSON
You can import issues and other data into Jira Cloud using a JSON file. The JSON format must follow Jira's import schema.
To import:
* Go toSettings > System > External System Import.
* SelectJSONand upload the JSON file.
* Map fields and configurations as prompted.Note: JSON imports are useful for custom migrations or backups.(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Why This Fits: JSON is a supported format for the Jira import wizard, making it a correct choice.
* CSV (Option F):
* The Jira import wizard supports importing data from CSV files, which can include issues, users, and other data. CSV imports are commonly used for bulk issue creation or migration from other systems.
* Exact Extract from Documentation:
Import data from CSV
The CSV importer allows you to import issues, users, and other data into Jira Cloud from a CSV file.
To import:
* Go toSettings > System > External System Import.
* SelectCSVand upload the file.
* Map CSV columns to Jira fields and configure settings.Note: Ensure the CSV file is properly formatted to avoid errors.(Source: Atlassian Support Documentation,
"Import data to Jira Cloud")
* Why This Fits: CSV is a supported format for the Jira import wizard, making it a correct choice.
* Why Other Options Are Incorrect:
* Microsoft Excel (Option A):
* The Jira import wizard does not directly support Microsoft Excel files (.xlsx, .xls). To import Excel data, it must first be converted to CSV format.
* Extract from Documentation:
Jira does not support direct imports from Excel files. Save Excel files as CSV and use the CSV importer to bring data into Jira.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Bitbucket (Option C):
* Bitbucket is not a supported source for the Jira import wizard. While Bitbucket integrates with Jira for development workflows (e.g., commits, pull requests), it does not provide issue or project data for import.
* Extract from Documentation:
Bitbucket integrates with Jira for development tools but is not a source for the Jira import wizard.
(Source: Atlassian Support Documentation, "Integrate Jira with Bitbucket")
* GitHub (Option D):
* GitHub is not a supported source for the Jira import wizard. While GitHub can integrate with Jira for development workflows, importing issues or projects from GitHub requires third-party apps or manual export to CSV/JSON.
* Extract from Documentation:
GitHub is not supported by the Jira import wizard. Use third-party apps or export GitHub data to CSV or JSON for import.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Additional Notes:
* The Jira import wizard is accessed viaSettings > System > External System Importand requires Jira administratorprivileges.
* Other supported sources (not listed in the options) include Jira Server/Data Center, Asana, and Monday.com, but Trello, JSON, and CSV are the correct matches here.
:
Atlassian Support Documentation:Import data to Jira Cloud
Atlassian Support Documentation:Integrate Jira with Bitbucket
NEW QUESTION # 29
An issue is showing the Time Tracking section as follows:
There is clearly an hour's difference between the Original and Remaining estimates. Identify two possible reasons Logged Time is showing as Not Specified. (Choose two.)
- A. The remaining estimate was adjusted without logging any effort.
- B. The original estimate was increased.
- C. The hour's work was logged via a REST call by the user.
- D. The work log would have exceeded the project's time allowance, so it cannot be counted.
- E. Time tracking was not enabled when the work was logged.
- F. You do not have view permission to see the logged work.
Answer: A,E
Explanation:
Reference: https://confluence.atlassian.com/adminjiraserver/configuring-time-tracking-938847808.html
NEW QUESTION # 30
You are the site and organization admin of a Jira Software and Confluence instance.
You are the only administrator and you don't have any Trusted users.
Users currently cannot send invitations to anyone. You need to control the number of licenses used.
Therefore, you want to either invite individual users or approve individual user requests.
Which site access setting will meet this requirement? (Choose one)
- A. Enable existing users to send invitations to anyone
- B. Don't approve any domain
- C. Approve your organization domain only
- D. Enable Jira Software and Confluence invite links
- E. Approve any domain
Answer: E
NEW QUESTION # 31
You need to create a filter that shows only issues that were created during the last calendar month. Identify the correct JQL query.
- A. createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)
- B. created changed during (startOfMonth(), endOfMonth())
- C. created >= startOfMonth(-1) AND created <= endOfMonth(-1)
- D. createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1)
Answer: A
Explanation:
To create a filter that shows issues created during the last calendar month, the JQL query must use the createdDatefield with thestartOfMonth(-1m)andendOfMonth(-1m)functions to define the time range. The correct query iscreatedDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)(Option D).
* Explanation of the Correct Answer (Option D):
* ThecreatedDatefield represents the date an issue was created. ThestartOfMonth(-1m)function returns the first day of the previous month (e.g., April 1, 2025, for May 2025), andendOfMonth (-1m)returns the last day of the previous month (e.g., April 30, 2025). The querycreatedDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)selects issues created within this range, covering the entire last calendar month.
* Exact Extract from Documentation:
Search for issues using JQL
ThecreatedDatefield (orcreatedalias) stores the creation date of an issue. Use date functions like startOfMonth()andendOfMonth()to define time ranges.
Examples:
* createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m) returns issues created in the previous calendar month.
* Use-1mto indicate one month ago.Note: Ensure date fields use>=and<=for inclusive ranges.
(Source: Atlassian Support Documentation, "Search for issues using JQL")
* Why This Fits: The query in Option D correctly usescreatedDate,startOfMonth(-1m), and endOfMonth(-1m)withANDto define the last calendar month, making it the correct answer.
* Why Other Options Are Incorrect:
* created changed during (startOfMonth(), endOfMonth()) (Option A):
* Thechanged duringoperator is used for fields that track changes (e.g., status, assignee), not for static fields likecreated. Additionally,startOfMonth()andendOfMonth()without-1 mrefer to the current month, not the last month.
* Extract from Documentation:
Thechanged duringoperator is invalid for thecreatedfield. Use>=and<=for date comparisons.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1) (Option B):
* TheORoperator creates a logical error, selecting issues created after the start of the previous monthorbefore the end of the previous month, which includes almost all issues.
Additionally,-1is ambiguous and typically invalid without a unit (e.g.,-1mfor one month).
The correct operator isANDto define a range.
* Extract from Documentation:
UseANDto define a date range (e.g., createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1 m)).ORcreates an overly broad range.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* created >= startOfMonth(-1) AND created <= endOfMonth(-1) (Option C):
* The-1syntax without a unit (e.g.,-1m) is ambiguous and typically invalid in JQL. The correct syntax uses-1mto indicate one month ago. Additionally, whilecreatedis an alias for createdDate, the incorrect time unit makes this query invalid.
* Extract from Documentation:
Date functions require units likemfor months (e.g.,startOfMonth(-1m)). Without a unit, the query is invalid.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
* Additional Notes:
* The filter can be created inIssues > Search for issues, saved as a filter, and shared if needed.
* Thecreatedalias can be used instead ofcreatedDate, butcreatedDateis more explicit and matches the options.
* Ensure the Jira instance's timezone aligns with the expected month range.
:
Atlassian Support Documentation:Search for issues using JQL
Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Advanced searching - functions reference
NEW QUESTION # 32
You created a new project and need to configure notifications.
Managers should be notified when
* Someone mentions them while adding or editing a comment
* The issue assignee or reporter is changed
* Issue links are added or deleted
You assume that users have not turned off any notifications through their Personal settings Identify the two notification events to which managers should definitely be added (Choose two)
- A. Issue Assigned
- B. Issue Deleted
- C. Issue Commented
- D. Generic Event
- E. Issue Updated
Answer: A,E
NEW QUESTION # 33
Henry was recently assigned multiple issues in a classic software project. He has not received any email notifications about the assignment of these issues but he received notifications about other changes to issues from this and other projects.
Identify two possible reasons (Choose two)
- A. The Issue Updated event does not list the current assignee as a recipient in the project's notification scheme
- B. The Issue Assigned event does not list the current assignee as a recipient in the projects notification scheme
- C. Henry is missing the Assignable User project permission in the Jira project
- D. Henry is missing the Browse Projects project permission in the Jira project
- E. Henry adjusted his personal email notification preference to not notify him when he is the assignee of an issue
Answer: A,B
NEW QUESTION # 34
A user says she can see the Ready for Testing transition but cannot successfully execute it.
Why can't the user execute this transition?
- A. A Condition on the transition requires the user to be in the Developer role.
- B. A Validator on the workflow transition requires the user to be in the Developer role.
- C. The status property of In Progress prevents the Developer role from executing the transition.
- D. The status property of Code Review prevents the Developer role from executing the transition.
Answer: C
NEW QUESTION # 35
You were asked to modify the only workflow in a company-managed project. Which two requirements can be satisfied using only out-of-box functionality? (Choose two.)
- A. Only members of Testers project role can transition to Passed.
- B. Automatically clear Assignee when transitioning to Pending.
- C. Automatically set Due Date based on the issue type.
- D. Automatically reassign an issue when Priority is edited.
- E. Only a subset of project users should be able to create epics.
Answer: A,B
Explanation:
In a company-managed project, workflows define the statuses and transitions for issues. Modifying a workflow using out-of-box functionality involves addingconditions,validators,post functions, orproperties to transitions. The two requirements that can be satisfied using only out-of-box functionality are automatically clear Assignee when transitioning to Pending(Option C) andonly members of Testers project role can transition to Passed(Option E).
* Explanation of the Correct Answers:
* Automatically clear Assignee when transitioning to Pending (Option C):
* This requirement can be met by adding apost functionto the workflow transition to the Pendingstatus. The out-of-boxClear Field Valuepost function can be used to clear the Assigneefield during the transition.
* Exact Extract from Documentation:
Configure workflow post functions
Post functions are executed after a transition is completed and can update issue fields or perform other actions. Out-of-box post functions include:
* Clear Field Value: Clears the value of a specified field (e.g., Assignee).To add a post function:
* Go toSettings > Issues > Workflows.
* Edit the workflow and select the transition to Pending.
* Add theClear Field Valuepost function and chooseAssignee.Note: Post functions are executed automatically during the transition, requiring no additional configuration.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Why This Fits: TheClear Field Valuepost function is an out-of-box feature that directly clears theAssigneefield during the transition toPending, satisfying the requirement without custom scripting or apps.
* Only members of Testers project role can transition to Passed (Option E):
* This requirement can be met by adding aconditionto the workflow transition to thePassed status. The out-of-boxUser Is In Project Rolecondition can restrict the transition to members of theTestersproject role.
* Exact Extract from Documentation:
Configure workflow conditions
Conditions restrict who can execute a workflow transition. Out-of-box conditions include:
* User Is In Project Role: Allows only users in a specified project role (e.g., Testers) to perform the transition.To add a condition:
* Go toSettings > Issues > Workflows.
* Edit the workflow and select the transition to Passed.
* Add theUser Is In Project Rolecondition and select theTestersrole.Note: Conditions are evaluated before the transition is displayed, ensuring only authorized users see the option.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Why This Fits: TheUser Is In Project Rolecondition is an out-of-box feature that restricts thePassedtransition to theTestersproject role, satisfying the requirement without custom scripting or apps.
* Why Other Options Are Incorrect:
* Automatically set Due Date based on the issue type (Option A):
* Out-of-box post functions allow setting a field to a specific value (e.g.,Update Issue Field) but do not support conditional logic based on issue type (e.g., setting different due dates for different issue types). This requirement would require a scripted post function or an automation rule, which goes beyond out-of-box workflow functionality.
* Extract from Documentation:
Out-of-box post functions can update fields with static values (e.g., set Due Date to a specific date).
Conditional logic based on issue type requires automation rules or third-party apps.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Only a subset of project users should be able to create epics (Option B):
* Creating epics is controlled by theCreate Issuespermission in the project's permission scheme, not by workflow settings. While permissions can be restricted to a subset of users (e.g., a group or role), this is not a workflow modification. Additionally, restricting epic creation specifically (versus other issue types) requires issue type-specific permissions, which are not supported out-of-box without advanced configuration or apps.
* Extract from Documentation:
TheCreate Issuespermission controls who can create issues, including epics. Issue type-specific restrictions require advanced permission schemes or apps, not workflow changes.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Automatically reassign an issue when Priority is edited (Option D):
* Reassigning an issue when thePriorityfield is edited is not possible with out-of-box workflow post functions, as post functions are tied to transitions, not field edits. This requirement would require a Jira automation rule or a scripted listener, which goes beyond out-of-box workflow functionality.
* Extract from Documentation:
Post functions are executed during workflow transitions, not field edits. To react to field changes like Priority, use Jira automation or third-party apps.
(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")
* Additional Notes:
* Modifying workflows requiresJira administratorprivileges, as workflows are managed at the system level (Settings > Issues > Workflows).
* Out-of-box functionality refers to native Jira features without scripting, third-party apps, or automation rules. Options C and E leverage standard post functions and conditions, while A, B, and D require additional logic or non-workflow configurations.
:
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Automate your Jira Cloud instance
NEW QUESTION # 36
Billie needs to perform various restricted tasks in the system. You must decide whether to grant her site admin or organization admin privileges.
Identify two reasons why you must make her an organization admin (Choose two)
- A. Billie needs to enable other users to be site or product admins
- B. Billie needs to log in as other users for troubleshooting user accounts
- C. Billie needs to enable other users to be organization admins
- D. Billie needs to remove users from the site
- E. Billie needs to make changes to user's profiles
Answer: C,D
NEW QUESTION # 37
You have a project with several issue types, associated unique workflows, and a number of components.
The decision has been made to have all new issues assigned automatically.
To that end, you've set default assignee(s) for the project lead, component leads, and removed the Assignee field from the screens associated with the Create Issue operation.
One of the issue types is still being created without an Assignee.
What is the most likely cause of the problem?
- A. The assignee is being set to Unassigned in the first post-function of the create transition.
- B. The post function Assign to Lead Developer is missing in the create transition.
- C. Users creating this issue type do not have the Assign Issue permission.
- D. The issue type's field configuration for Component/s is not set to Required.
- E. The default assignee for the issues' component is still set to Unassigned.
Answer: A
NEW QUESTION # 38
Which three factors should you consider when deciding between Jira Cloud and Jira Server? (Choose three.)
- A. the number of workflows you will require
- B. the commercial apps you would like to use
- C. the amount of time required for system administration
- D. the ability to integrate with an external user directory (e.g. company LDAP directory)
- E. the ability to integrate Jira with a cloud-based source repository (e.g. Bitbucket)
- F. the availability of a REST API
Answer: B,C,F
Explanation:
Reference: https://confluence.atlassian.com/cloud/compare-atlassian-cloud-vs-server-744721664.html
NEW QUESTION # 39
......
New Real ACP-120 Exam Dumps Questions: https://www.newpassleader.com/ATLASSIAN/ACP-120-exam-preparation-materials.html
ACP-120 Exam Dumps - ATLASSIAN Practice Test Questions: https://drive.google.com/open?id=1Q9-r3sjo7VXb3Ja410uJbxoI0iuYloFH