Easily To Pass New ATLASSIAN ACP-120 Dumps with 77 Questions
Latest ACP-120 Study Guides 2025 - With Test Engine PDF
ATLASSIAN ACP-120: Jira Cloud Administrator Exam is a certification program designed to test an individual’s knowledge and skills in administering Jira Cloud. ACP-120 exam is intended for individuals who are responsible for administering and configuring Jira Cloud for their organization's needs. Jira Cloud Administrator certification is recognized globally and validates the expertise of the individual in managing and implementing Jira Cloud.
NEW QUESTION # 32
You have been asked to take on the administration of a second Jira installation in your company.
You were given the following information about user accounts:
- The company standard is to use Active Directory (AD) to provide user accounts.
- There are several Active Directory systems in use by different business units.
- The second Jira is not to be merged with your main Jira.
- The main Jira system is connected to Active Directory for user accounts.
- The second Jira is using internal user accounts, not Active Directory.
- People using the second Jira are using the same login ID as they would use in Active Directory.
- Your company would like to use Single Sign-on (SSO) but has not yet implemented it for either Jira system.
Which authentication method should you recommend?
- A. Set up a Crowd server to get the user lists from all internal directories and AD, and use AD directly for the password checking.
- B. Set up a Crowd server to pull in all the AD services, and plan to migrate internal users.
- C. Change the new Jira to link directly to the required AD servers.
- D. Change the new Jira to use your main Jira's directory services, as that is already reading your Active Directory services.
Answer: A
NEW QUESTION # 33
You want to rename an issue type. What might be impacted by this change?
- A. Issue type schemes
- B. Issue type screen schemes
- C. Swimlanes by queries
- D. Workflow schemes
- E. Custom field contexts
Answer: C
Explanation:
Renaming an issue type in Jira Software Cloud changes its display name, which can impact configurations or features that reference the issue type by name, particularly in JQL queries or user-defined settings. The element most likely to be impacted isswimlanes by queries(Option D), as swimlanes often use JQL queries that include issue type names.
* Explanation of the Correct Answer (Option D):
* Swimlaneson Jira boards (e.g., Kanban or Scrum) can be configured to use JQL queries to group issues (e.g., issuetype = Bug). If a swimlane's JQL query references the issue type being renamed (e.g., issuetype = Task), renaming the issue type (e.g., toStory) will cause the query to no longer match issues of the renamed type, breaking the swimlane's functionality. These queries must be updated to reflect the new issue type name.
* Exact Extract from Documentation:
Configure board swimlanes
Swimlanes on Jira boards can be based on JQL queries (e.g., issuetype = Bug).
Impact of renaming issue types:
* JQL queries referencing the issue type name (e.g., issuetype = Task) will no longer match issues if the issue type is renamed (e.g., to Story).To update:
* Go toBoard settings > Swimlanes.
* Update the JQL query to use the new issue type name.Note: Renaming an issue type can affect any JQL-based feature, including swimlanes, filters, and dashboards.(Source:
Atlassian Support Documentation, "Configure boards in Jira Cloud")
* Why This Fits: Renaming an issue type impactsswimlanes by queriesbecause JQL queries in swimlane configurations may reference the issue type name, requiring updates to maintain functionality, making Option D the correct answer.
* Why Other Options Are Incorrect:
* Issue type schemes (Option A):
* Issue type schemesdefine which issue types are available in a project. Renaming an issue type changes its display name globally but does not alter the scheme's structure or associations, as issue types are referenced by their internal IDs in schemes.
* Extract from Documentation:
Renaming an issue type updates its display name but does not affect issue type schemes, which use internal IDs.
(Source: Atlassian Support Documentation, "Manage issue types in Jira Cloud")
* Issue type screen schemes (Option B):
* Issue type screen schemesmap screens to issue types for operations (Create, Edit, View).
These schemes reference issue types by their internal IDs, so renaming an issue type does not impact the scheme's configuration.
* Extract from Documentation:
Issue type screen schemes use issue type IDs, not names. Renaming an issue type does not require changes to screen schemes.
(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")
* Workflow schemes (Option C):
* Workflow schemesmap workflows to issue types. Like other schemes, they use issue type IDs, so renaming an issue type does not affect workflow assignments or configurations.
* Extract from Documentation:
Workflow schemes reference issue types by ID. Renaming an issue type has no impact on workflow schemes.
(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Custom field contexts (Option E):
* Custom field contextsdefine the projects and issue types where a custom field is available.
Contexts also use issue type IDs, so renaming an issue type does not require changes to the context configuration.
* Extract from Documentation:
Custom field contexts use issue type IDs. Renaming an issue type does not affect field contexts.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Additional Notes:
* Renaming an issue type is done inSettings > Issues > Issue typesand requiresJira administrator privileges.
* Other JQL-based features (e.g., filters, dashboards, automation rules) may also be impacted if they reference the issue type name, butswimlanes by queriesis the most directly affected among the options.
* To minimize impacts, use issue type IDs in JQL queries (e.g., issuetype = 10001), though this is less common.
:
Atlassian Support Documentation:Configure boards in Jira Cloud
Atlassian Support Documentation:Manage issue types in Jira Cloud
Atlassian Support Documentation:Configure screen schemes in Jira Cloud
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Manage custom fields in Jira Cloud
NEW QUESTION # 34
You need to implement a change to several classic projects in your Jira instance
* A defined set of users needs to be able to create issues on behalf of other users It is important to note that
* Project administrators should be able to decide which users are able to perform this operation
* Some projects use a shared permission scheme
Which combined use of two administrative items will meet this requirement? (Choose two)
- A. User group
- B. Project permission
- C. Individual users
- D. Project role
- E. Global permission
Answer: B,D
NEW QUESTION # 35
Peter is building a workflow in his team-managed project. He can add several rules to his workflow except for one rule. Identify that rule.
- A. Rule to reopen Sub-tasks when reopening Stories.
- B. Rule to ensure only the Reporter can close bugs.
- C. Rule to ensure only Peter can approve Stories.
- D. Rule to clear the Assignee when closing.
- E. Rule to clear the Description when reopening.
Answer: A
Explanation:
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
NEW QUESTION # 36
You need to make changes to the time tracking feature in Jira. What configuration can be controlled globally across all projects?
- A. The default tracking time unit, unless users explicitly specify one
- B. The ability to log work on issues for specific groups
- C. The requirement of an original estimate when creating issues
- D. The availability of time tracking fields on standard versus sub-task issue types
- E. The ability to edit or delete their own or other users' worklogs for specific users
Answer: A
Explanation:
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 in Settings > 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.
:
Atlassian Support Documentation:Configure time tracking in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Configure field settings
NEW QUESTION # 37
Mira is working on a story. All of a sudden, the links to all three bugs related to the story disappeared. All issues including the story and the three bugs are tracked in the DEV project, which is a classic Software project.
Which four can explain the situation (Choose four)
- A. Link issues permission was revoked for Mira
- B. The links to the bugs were deleted
- C. Browse Projects permission was revoked for Mira
- D. The linked bugs were deleted
- E. A security level was applied to the linked bugs
- F. Issue linking was disabled globally
Answer: B,D,E,F
NEW QUESTION # 38
Three team members have left the company and their issues need to be re-assigned to various - users.
All of their issues are in the Marketing project which uses the Default Notification Scheme. The scheme has never been updated.
How do you inform the new assignees about their re-assigned issues?
- A. Add an announcement banner to the marketing project to inform team members.
- B. Perform bulk operations to re-assign the issues and notify the new assignees.
- C. Use the Send email feature to inform the individual new assignees.
- D. Add an announcement banner to each new assignee's dashboard.
- E. Perform a single bulk operation to mention all new assignees in a comment.
Answer: D
NEW QUESTION # 39
You receive workflow configuration requirements for issues in the Closed status. They are as follows:
Users must NOT be able to edit issues in this status.
Jira administrators must be able to edit issues in this status.
Only users in the release-managers group should see the transition to the Re-opened status Which combination of two workflow configuration items should you use to meet these requirements?
(Choose two.)
- A. Validators
- B. Conditions
- C. Properties
- D. Post functions
- E. Triggers
Answer: A,B
NEW QUESTION # 40
Your management team needs to see a list of only those issues that were resolved in the previous week, from Sunday to Saturday. The list needs to be sent to them each week on Tuesdays. You plan to create a saved filter and filter subscription to do this.
Which JQL query will Mum the correct results?
- A. resolved ,= start0fWeek(-1) AND resolved start0fWeek0
- B. resolved end0fWeek(1)
- C. resolved>=startOfDay(-7) AND resolved < startOfDay()
- D. status changed TO RESOLVED BEFORE startOfWeek()
Answer: A
Explanation:
A). Incorrect. -resolved >. end0fWeek(1. will return all issues resolved this week, up until Tuesday when the filter is sent.
B). Correct. ^resolved ,= start0fWeek(1 AND resolved < start0fWeeklr ensures that only issues created in the previous week, from Sunday to Saturday, are returned by the query. The start0fWeek0 function returns Sunday 00:00 by defauk.
C). Incorrect. Resolved issues do not necessarily have their status changed to Resolved. Issues may be resolved with a status of Done or Closed as long as the Resolution field is set. Additionally, the query will return all issues that have ever been transitioned to Resolved status, not just from last Sunday to Saturday.
D). Incorrect. -resolved >= start0fDay(-7). is actually a Tuesday. So this filter will return all issues resolved from Tuesday of last week to Monday of this week.
NEW QUESTION # 41
Your HR project has two issue types:
- Join
- Leave
Both issue types share a field configuration, screens and the workflow.
You currently use the Due Date system field to indicate when someone actually joins or leaves.
New HR staff members complain that using the Due Date field is not very intuitive.
How can you help your HR team?
- A. - Create individual Join Date and Leave Date custom fields to replace the Due Date field.
- Appropriately migrate existing data from the Due Date field to the new custom fields.
- Remove the Due Date field from all project screens. - B. - Create individual field contexts for each issue type.
- Label the Due Date field as Join Date and Leave Date in their respective contexts.
- Associate each context with its matching issue type. - C. - Create individual Join Date and Leave Date custom fields to replace the Due Date field.
- Create separate screens for each issue operation and issue type.
- Delete the Due Date field. - D. - Rename the Due Date field to Join Date and create a separate Leave Date custom field.
- Create new screens for the Leave issue type and replace the Due Date field with the newly created field.
- Migrate existing field values to the new Leave Date field.
Answer: B
NEW QUESTION # 42
Gary complains that he is not getting any notifications when issues are updated.
According to the notification helper, he should receive notifications for all issues he is watching. His coworkers confirm they receive those notifications and they regularly update issues that he is watching.
Which update to Gary's personal settings must have occurred (Choose one)
- A. The setting You make changes to the issue was disabled
- B. The setting Watch your issues was disabled
- C. The setting Email notifications format was changed
- D. The setting You're watching the issue was disabled
Answer: D
NEW QUESTION # 43
A new user needs access to all applications of your Atlassian Cloud site to configure projects without consuming any user licenses.
Select two items which, when combined, will satisfy this requirement? (Choose two)
- A. Trusted user role
- B. Administration access
- C. Site access
- D. Individual users
- E. User groups
- F. Product access
Answer: B,C
NEW QUESTION # 44
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 default assignee for the issues' component is still set to Unassigned.
- C. Users creating this issue type do not have the Assign Issue permission.
- D. The post function Assign to Lead Developer is missing in the create transition.
- E. The issue type's field configuration for Component/s is not set to Required.
Answer: A
NEW QUESTION # 45
Jon needs to create groups and manage membership in groups. Which administrator privilege does Jon need?
- A. System administrator
- B. Jira administrator
- C. Project administrator
- D. Product Admin role for Jira
- E. Organization admin
Answer: B
Explanation:
Creating groups and managing group membership in Jira Software Cloud are system-level tasks that require theJira administratorprivilege. This privilege allows Jon to access user management settings and perform group-related actions.
* Explanation of the Correct Answer (Option D):
* TheJira administratorprivilege grants users the ability to manage global settings, including creating groups and managing their membership. This includes adding or removing users from groups, which is necessary for Jon's requirements.
* Exact Extract from Documentation:
Jira administrator permissions
Jira administrators can manage global settings, including:
* Creating and deleting groups.
* Adding or removing users from groups.
* Managing global permissions and user access.To create or manage groups:
* Go toSettings > User management > Groups.
* Create a new group or edit existing group membership.Note: Only Jira administrators or organization admins with user management permissions can perform these actions.(Source:
Atlassian Support Documentation, "Manage groups in Jira Cloud")
* Why This Fits: TheJira administratorprivilege directly enables Jon to create groups and manage their membership, making Option D the correct choice.
* Why Other Options Are Incorrect:
* Organization admin (Option A):
* Organization admins manage the Atlassian organization, including user access to products and billing. While they can manage users and groups at the organization level, creating groups specifically in Jira requiresJira administratorprivileges unless the organization admin also has this role.
* Extract from Documentation:
Organization admins manage user access, billing, and security at the Atlassian organization level. Managing Jira-specific groups requires Jira administrator privileges.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Product Admin role for Jira (Option B):
* TheProduct Adminrole for Jira grants access to manage product-specific settings, such as user access to Jira Software. However, creating and managing groups is a system-level task that requiresJira administratorprivileges.
* Extract from Documentation:
Product admins manage user access to specific products (e.g., Jira Software). Group management requires Jira administrator or organization admin privileges.
(Source: Atlassian Support Documentation, "Manage product access")
* System administrator (Option C):
* The termsystem administratoris not a standard role in Jira Cloud. In some contexts, it may refer toJira administratorsororganization admins, but it is not a distinct privilege for group management.
* Extract from Documentation:
Jira Cloud uses roles like Jira administrator and organization admin. There is no distinct "system administrator" role for group management.
(Source: Atlassian Support Documentation, "Manage users and groups")
* Project administrator (Option E):
* Project administrators manage settings for specific projects (e.g., permissions, components) but cannot create or manage groups, as these are global settings.
* Extract from Documentation:
Project administrators manage project-specific settings but cannot access global settings like user or group management.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Additional Notes:
* Jon's tasks require access toSettings > User management > Groups, which is restricted toJira administrators.
* If Jon is also an organization admin, he might have overlapping permissions, but theJira administratorrole is the most direct for group management in Jira.
:
Atlassian Support Documentation:Manage groups in Jira Cloud
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage project permissions
NEW QUESTION # 46
In his personal settings, Bob has the setting "Email notifications for issue activity set to "Don't send me email notifications".
Identify two reasons why Bob continues to receive some email notifications from Jira (Choose two)
- A. Bob was added as a watcher of an issue
- B. Bob has the Watch your issues setting enabled
- C. Bob is mentioned directly in a comment
- D. Bob has been subscribed to several filters
- E. Bob was sent an email via the Send email feature in Jira
Answer: D,E
NEW QUESTION # 47
A new team requests a Jira project. They must be able to:
* Manage and prioritize all work from a central backlog.
* Track progress with a burndown chart.
* Move pre-production defects and production defects through a different QA process.
* Have the project share its schemes with another project in the future.
Which project type fulfills these requirements?
- A. Team-managed Scrum
- B. Company-managed Scrum
- C. Team-managed Kanban
- D. Company-managed Kanban
Answer: B
Explanation:
The requirements for the new Jira project include a central backlog, burndown chart, different QA processes for defect types, and the ability to share schemes with another project. Thecompany-managed Scrumproject type (Option B) best fulfills all these requirements due to its support for Scrum boards, burndown charts, flexible workflows, and shared configurations.
* Explanation of the Correct Answer (Option B):
* Manage and prioritize all work from a central backlog:
* Company-managed Scrum projects include aScrum boardwith a central backlog where issues (e.g., Stories, Defects) can be managed and prioritized.
* Exact Extract from Documentation:
Company-managed Scrum projects
Company-managed Scrum projects provide a Scrum board with a central backlog for managing andprioritizing work.
To access:
* Go toProject > Backlog.
* Prioritize issues by dragging and dropping.Note: The backlog supports all issue types in the project.(Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")
* Track progress with a burndown chart:
* Company-managed Scrum projects supportburndown chartsin sprint reports, which track progress based on Story Points or issue count during a sprint.
* Exact Extract from Documentation:
Burndown charts in Scrum projects
Company-managed Scrum projects include burndown charts in sprint reports to track progress.
To view:
* Go toProject > Reports > Burndown Chart.
* Select the sprint to view progress.Note: Burndown charts require sprints and Story Points or issue counts.(Source: Atlassian Support Documentation, "Manage Scrum projects in Jira Cloud")
* Move pre-production defects and production defects through a different QA process:
* Company-managed projects allow different issue types (e.g., Pre-production Defect, Production Defect) to use distinct workflows via aworkflow scheme. This enables separate QA processes (e.g., different statuses or transitions) for each defect type.
* Exact Extract from Documentation:
Configure workflows in company-managed projects
A workflow scheme maps workflows to issue types. Different issue types (e.g., Pre-production Defect, Production Defect) can use different workflows to support unique processes.
To configure:
* Go toSettings > Issues > Workflow schemes.
* Assign workflows to issue types in the project's scheme.Note: Company-managed projects support complex workflow configurations.(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Have the project share its schemes with another project in the future:
* Company-managed projects use shared configurations (e.g., permission schemes, workflow schemes, issue type schemes) that can be reused by other projects. This allows the new project to share its schemes with another project in the future.
* Exact Extract from Documentation:
Shared configurations in company-managed projects
Company-managed projects use schemes (e.g., workflow, permission, issue type) that can be shared across multiple projects.
To share:
* Create a project with a shared configuration inSettings > Projects > Create project.
* Select the same schemes for another project.Note: Team-managed projects have project-specific configurationsand cannot share schemes.(Source: Atlassian Support Documentation, "Create a project in Jira Cloud")
* Why This Fits: Thecompany-managed Scrumproject type supports a central backlog, burndown charts, distinct workflows for defect types, and shared schemes, fully meeting all requirements.
* Why Other Options Are Incorrect:
* Company-managed Kanban (Option A):
* While company-managed Kanban projects support a central backlog (Kanban board) and shared schemes, they do not natively provideburndown charts, which are specific to Scrum projects for tracking sprint progress. Additionally, while different workflows for defect types are possible, Kanban projects are less aligned with sprint-based tracking like burndown charts.
* Extract from Documentation:
Company-managed Kanban projects use a Kanban board but do not include burndown charts, which are specific to Scrum sprints.
(Source: Atlassian Support Documentation, "Manage Kanban projects in Jira Cloud")
* Team-managed Scrum (Option C):
* Team-managed Scrum projects support a backlog, burndown charts, and simplified workflows. However, they do not support shared schemes, as configurations (e.g., workflows, permissions) are project-specific and cannot be reused by other projects.
Additionally, team-managed projects have limited workflow flexibility, making it harder to define distinct QA processes for defect types.
* Extract from Documentation:
Team-managed projects have project-specific configurations and cannot share schemes with other projects.
Workflows are simplified and may not support complex processes for multiple issue types.
(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")
* Team-managed Kanban (Option D):
* Team-managed Kanban projects support a Kanban board but lackburndown charts, as they do not use sprints. They also have project-specific configurations, preventing scheme sharing, and limited workflow flexibility for distinct QA processes.
* Extract from Documentation:
Team-managed Kanban projects do not support burndown charts or shared schemes. Workflows are project- specific and simplified.
(Source: Atlassian Support Documentation, "Manage team-managed projects in Jira Cloud")
* Additional Notes:
* Creating a company-managed Scrum project requiresJira administratorprivileges (Settings > Projects > Create project).
* The project can be configured with aScrum board,workflow schemefor distinct defect workflows, and shared schemes for future projects.
* Burndown charts require sprints and Story Points or issue counts to be configured.
:
Atlassian Support Documentation:Manage Scrum projects in Jira Cloud
Atlassian Support Documentation:Manage Kanban projects in Jira Cloud
Atlassian Support Documentation:Manage team-managed projects in Jira Cloud Atlassian Support Documentation:Configure workflow schemes Atlassian Support Documentation:Create a project in Jira Cloud
NEW QUESTION # 48
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. Henry is missing the Assignable User project permission in the Jira project
- B. The Issue Assigned event does not list the current assignee as a recipient in the projects notification scheme
- C. Henry is missing the Browse Projects project permission in the Jira project
- D. The Issue Updated event does not list the current assignee as a recipient in the project's notification scheme
- E. Henry adjusted his personal email notification preference to not notify him when he is the assignee of an issue
Answer: B,D
NEW QUESTION # 49
......
ACP-120 Dumps and Exam Test Engine: https://2cram.actualtestsit.com/ATLASSIAN/ACP-120-exam-prep-dumps.html