Skip to document

Acp 120 exam topics list

just practice
Course

ancient society (PG -C102)

5 Documents
Students shared 5 documents in this course
Academic year: 2017/2018
Uploaded by:
0followers
3Uploads
0upvotes

Comments

Please sign in or register to post comments.

Preview text

ACP-120 Exam Topics List

1 Access, Permissions, Security (28% of the exam) Jira Cloud administrators are responsible for access at all levels: organization, product, project, and issue. This includes both licenced and anonymous access, managed and unmanaged accounts, appropriate administrator privileges, and use of groups and project roles, in both team-managed and company-managed projects. This also requires understanding the interdependence between product access, global permissions, project permissions, workflow conditions, and issue-level-security. 1 Determine appropriate administrator privileges The three admin types: org admin, Jira admin, project admin Granting the admin privilege to each admin type What actions can be performed by each admin type Give users admin permissions Make a user an org admin Make a user a site admin Make a user a product admin Project admins 1 Configure global permissions Purpose of each global permission Global permissions are granted to groups Manage global permissions Grant global permissions to a group of users How do Jira permissions work 1 Configure project permissions Distinction between access in team-managed projects and permission schemes in company-managed projects Purpose of each permission Which permissions are needed in combination When to use project roles versus groups Configuring user/group custom fields in permissions Relationship between certain project permissions and global settings (e. issue-linking and Link Issues permission) Manage project permissions Project admins Manage project roles Permissions for company-managed projects Add users, groups, or roles to a permission scheme and grant their project permissions Permissions for team-managed projects Manage how people access your team-managed project Add people to team-managed projects Should I use Project Roles or Groups? 1 Configure issue-level security Use cases for using issue-level security Using Reporter, Assignee, and user/group custom fields as Security Level entries Configurations required to enable issue-level security in a project Use of restrictions in team-managed projects Issue level security inheritance Configure issue security schemes Apply comment permissions Restrict access to an issue type in team- managed projects Issue Security in Jira 2 General Project Configuration (11% of the exam) Jira Cloud administrators are responsible for creating and configuring the projects, including determining the correct project type, which template to use, configuring project details and implementing components and versions. 2 Understand project types, templates, and shared configurations Know differences between team-managed and company managed projects, including features, boards, and configuration options Determine which project type to use - team-managed or company-managed project along with scrum versus Kanban Project templates and how to select them Advantages and limitations of shared configurations for company-managed project What are team-managed and company- managed projects What are the project templates Manage and administer team-managed projects Create a project that shares its configuration with another project 2 Configure project details and sidebar Project details configuration Impact of modifying a project’s name and/or key Configure Projects Edit a project's details Things to consider before changing a project key 2 Manage versions Implications of releasing a version with unresolved issues Merge, delete and release a version Version naming/unique names What is a version Release your team's work in versions ID Objective Resources

2 Configure components and auto-assignments Understand how default assignee is determined when multiple components are selected Setting a project default assignee Understand how default assignee is determined with a combination of project default assignee and component assignees Organize work with components Add or change your project's default assignee 3 Issue Types, Fields, Screens (18% of the exam) Jira Cloud administrators are responsible for the creation and maintenance of issue types, fields, screens and their schemes. They need to know how to configure issue layouts in both team and company-managed projects. They must understand the use cases for the creation of new issue types, and custom fields and how to utilize custom field context. Jira admins must also understand the use cases for epics and sub-tasks, for both scrum and Kanban projects. 3 Configure issue types Creating issue types and issue type schemes Impact of changing an issue type name Mapping issue types to workflows, issue type screen schemes and field configuration schemes in company-managed projects Use cases for utilizing sub-tasks Understand how time-tracking on sub-tasks roll up to parent Use cases for utilizing epics including cross-project epics Creating issue types in team-managed projects What are issue types Add, edit, and delete an issue type Configure sub-tasks What are issue type schemes Add, edit, and delete an issue type scheme Set up issue types in team-managed projects 3 Configure fields Creating custom fields including using context Field formatting in field configurations including text rendering, hidden, and required fields Adding fields to team-managed projects Add, edit, and delete a field configuration Change a field configuration Associate field behavior with an issue type Specify field behavior Create a custom field Configure a custom field Add a context to a custom field Custom fields types in company-managed projects Add a context to a custom field Customize an issue's fields in team-managed projects Available custom fields for team-managed projects 3 Configure screens and issue layout Creating screens for company-managed projects Configuring issue layout in company-managed projects Configuring screens for issue types in team-managed projects Manage issue screens Configure field layout in the issue view Copy an issue layout to other projects How fields appear on your issues in team- managed projects 4 Workflows and Automation (14% of the exam) Jira Cloud administrators are responsible for creating usable and sustainable workflows including project-level customizations in both company and team-managed projects. They need to understand all parts of workflow configuration and the relationship between workflows and boards. Jira Cloud administrators must be able to interpret business requirements to create automation rules to perform repetitive tasks. Finally they must understand the relationship between project roles, permissions and automation rules. 4 Configure company-managed workflows Parts of workflows including statuses and transitions Parts of transitions including properties, conditions, validators, and post functions Relationship between statuses and boards Importance of setting resolution field How to set the resolution field Work with issue workflows Edit an issue workflow Configure advanced issue workflows Add a custom event Use workflow properties Use workflow validators for company managed projects Configure columns

6 Write advanced JQL queries JQL fields, including use of custom fields JQL functions and their available arguments JQL operators JQL keywords How to use parentheses in JQL statements to create clauses How to find issues for specific time and date ranges via JQL Limitations of basic search What is advanced searching in Jira Cloud Advanced search reference - JQL functions Advanced search reference - JQL fields Advanced search reference - JQL keywords Advanced search reference - JQL operators What is JQL: functions, history, and sorting JQL: Get started with advanced search in Jira Gain Project Insights through JQL Working with search results Perform a basic search 6 Configure filters, dashboards, subscriptions Global permission for sharing dashboards and filters How project permissions impact viewing shared filter results Creating shared filters and dashboards Creating and configuring a filter subscription, including scheduling options Using groups in filter subscriptions Troubleshooting filter subscriptions Using currentUser() function in filters and their subscriptions Save your search as a filter Prevent or remove public access Work with search results Subscribe to search results 6 Understand bulk operations Available options for bulk updates Relationship between project, issue, and workflow permissions to the availability of bulk update actions Relationship of workflow transitions and the availability of bulk update actions Field mapping during bulk update Potential implications of bulk update including replacing field values and sending notifications Limitations of moving issues between company-managed to team-managed projects via bulk update Edit multiple issues at the same time Migrate between team-managed and company- managed projects 7 System Administration (9% of the exam) Jira Cloud administrators need to understand how to create and manage global configurations including look and feel options, user default settings, links, and time tracking. They must also configure statuses, resolutions and priorities and understand the impact of modifying those items. Finally, Jira Cloud administrators must know how to import and export data including creating and restoring site backups. 7 Configure global user interface features Options for user default settings Options for the instance look and feel, and announcement banner Differences and relationship between user default settings and individual personal settings Impact of updating user default settings, on existing objects How to modify the Default dashboard Configure global settings Configure the look and feel of Jira applications Configure the default dashboard Use dashboard gadgets Configure the user default settings Manage your Jira personal settings 7 Configure attachments, issue links, app links, time-tracking globally Enabling and configuring estimation and time tracking Troubleshooting time tracking Enabling and configuring issue linking Configuring application and instance links Configure issue linking Use AppLinks to link to Atlassian products Create links in the application navigator Configure time tracking Configure estimation and tracking 7 Configure statuses, resolutions, priorities and sub-tasks globally Creating statues, resolutions and priorities Impact of renaming statuses, resolutions and priorities How to disable sub-tasks Impact of renaming workflow statuses in team-managed projects What are issue statuses, priorities, and resolutions Configure statuses, resolutions, and priorities Configure sub-tasks 7 Understand system backup and import Import options Steps for creating a backup, including media How to restore data from a backup Permissions needed to perform backup and restore actions How archived projects are handled during imports from backup Export data from Jira Cloud What gets migrated with Jira site import Import issues Import data from a CSV file Import data from Trello Import data from JSON

Was this document helpful?

Acp 120 exam topics list

Course: ancient society (PG -C102)

5 Documents
Students shared 5 documents in this course

University: Sikkim University

Was this document helpful?
ACP-120 Exam Topics List
1 Access, Permissions, Security (28% of the exam)
Jira Cloud administrators are responsible for access at all levels: organization, product, project, and issue. This includes both licenced and
anonymous access, managed and unmanaged accounts, appropriate administrator privileges, and use of groups and project roles, in both
team-managed and company-managed projects. This also requires understanding the interdependence between product access, global
permissions, project permissions, workflow conditions, and issue-level-security.
1.2 Determine appropriate administrator privileges
The three admin types: org admin, Jira admin, project admin
Granting the admin privilege to each admin type
What actions can be performed by each admin type
Give users admin permissions
Make a user an org admin
Make a user a site admin
Make a user a product admin
Project admins
1.3 Configure global permissions
Purpose of each global permission
Global permissions are granted to groups
Manage global permissions
Grant global permissions to a group of users
How do Jira permissions work
1.4 Configure project permissions
Distinction between access in team-managed projects and permission schemes in company-managed projects
Purpose of each permission
Which permissions are needed in combination
When to use project roles versus groups
Configuring user/group custom fields in permissions
Relationship between certain project permissions and global settings (e.g. issue-linking and Link Issues permission)
Manage project permissions
Project admins
Manage project roles
Permissions for company-managed projects
Add users, groups, or roles to a permission
scheme and grant their project permissions
Permissions for team-managed projects
Manage how people access your team-managed
project
Add people to team-managed projects
Should I use Project Roles or Groups?
1.5 Configure issue-level security
Use cases for using issue-level security
Using Reporter, Assignee, and user/group custom fields as Security Level entries
Configurations required to enable issue-level security in a project
Use of restrictions in team-managed projects
Issue level security inheritance
Configure issue security schemes
Apply comment permissions
Restrict access to an issue type in team-
managed projects
Issue Security in Jira
2 General Project Configuration (11% of the exam)
Jira Cloud administrators are responsible for creating and configuring the projects, including determining the correct project type, which
template to use, configuring project details and implementing components and versions.
2.1 Understand project types, templates, and shared configurations
Know differences between team-managed and company managed projects, including features, boards, and configuration options
Determine which project type to use - team-managed or company-managed project along with scrum versus Kanban
Project templates and how to select them
Advantages and limitations of shared configurations for company-managed project
What are team-managed and company-
managed projects
What are the project templates
Manage and administer team-managed projects
Create a project that shares its configuration with
another project
2.2 Configure project details and sidebar
Project details configuration
Impact of modifying a project’s name and/or key
Configure Projects
Edit a project's details
Things to consider before changing a project key
2.3 Manage versions
Implications of releasing a version with unresolved issues
Merge, delete and release a version
Version naming/unique names
What is a version
Release your team's work in versions
ID Objective Resources