Managing Jira Cloud Projects 온라인 연습
최종 업데이트 시간: 2025년06월06일
당신은 온라인 연습 문제를 통해 Atlassian ACP-620 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 ACP-620 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 150개의 시험 문제와 답을 포함하십시오.
정답:
정답:
Explanation:
Role:
- Project administrators can manage roles' membership.
- Only Jira administrators can create a new role.
- Roles are associated with project permissions.
- Each Jira project have default roles.
- Users and groups can be assigned roles.
Group:
- Only site administrators have access to create groups and assign users to the group.
- Groups can be associated with global and project permissions.
- Groups can be used in multiple Jira projects.
Reference:
- Managing project roles
- Create and update groups
정답:
Explanation:
These are the functionalities offered by the roadmap feature in Jira. It allows users to plan, track, manage, and forecast their work in a visual, easy-to-understand way. Users can filter issues by various criteria like assignee, component, or status and can even create new issues directly from the roadmap.
정답:
Explanation:
Average Age Report contains graph bars and a table showing the average number of days that issues were unresolved in a day over the past certain days.
If the below image is not visible, right-click the below image then click 'Open image in new tab'.
Resolution Time Report contains graph bars and a table showing the length of time taken to resolve a set of issues for a project/filter. This helps users identify trends and incidents which they can investigate further.
Single Level Group By Report shows a table of issues grouped by a particular field (including custom fields) for a filter. This helps users group search results by a field and see the overall status of each group.
Pie Chart Report shows a pie chart of issues for a project/filter grouped by a specified field. This helps users see the breakdown of a set of issues at a glance.
Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues.
Time Since Issues Report allows users to choose a date field and project/filter, then maps the issues against the date that the field was set. This can help users track how many issues were created, updated, etc, over a period of time.
정답:
Explanation:
'Make bulk changes', 'Manage group filter subscriptions', and 'Browse users and groups' are global permissions.
Other permissions are project permissions.
Explanation:
Reference:
- Manage global permissions
- Permissions for company-managed projects
정답:
Explanation:
This could occur if some statuses from the various project workflows are not mapped to the columns on the new Kanban board. In Jira, if an issue's status is not mapped to a column on the board, the issue will not be visible on the board. Hence, it's crucial to ensure that all relevant statuses are mapped to columns when setting up a new board that includes issues from multiple projects.
정답:
Explanation:
A team-managed project can only have a single board, which only belongs to that project.
A company-managed project can have multiple boards, including mixed team-managed or company-managed projects.
Users cannot directly create a board from the existing team-managed project, but they can use a saved filter. For example, users can create a saved filter that includes both company-managed and team-managed projects; then use that saved filter to create a new board. However, that board's location can only be located in the company-managed project.
정답:
Explanation:
On July 25th, there are:
- 4 issues in 'To Do'
- 1 issue in 'In Progress'
- 6 issues in 'Done'
정답:
Explanation:
All of the above JQL is incorrect. The correct answer is: summary ~ "user" OR summary ~ "developer" OR
summary ~ "tester"
summary ~ "user, developer, tester" is incorrect. This query will return issues that contain all three keywords (user, developer, and tester) in their summary.
summary ~ ("user", "developer", "tester") is incorrect. Operator '~' does not support the list value.
summary in ("user", "developer", "tester") is incorrect. The operator 'in' is not supported by the 'summary' field.
summary ~ "user" AND summary ~ "developer" AND summary ~ "tester" is incorrect. This query will return issues that contain all three keywords (user, developer, and tester) in their summary.
정답:
Explanation:
In Jira Query Language (JQL), you can use multiple ways to search for issues without labels. "labels = EMPTY", "labels = """, "labels = ''", and "labels is EMPTY" are all valid JQL queries to find issues that do not have any labels assigned to them.
Note that "labels = null" and "labels in (null)" are not valid JQL queries to find issues without labels. In JQL, "null" is not a recognized value.
정답:
Explanation:
In Jira, the board creator, Jira administrator, board administrator, and site administrator can manage the Jira board.
Project administrators do not necessarily have the permissions to manage a board unless they have been given explicit permissions or they were the ones who created the board. The permissions to manage the board include the ability to configure the board, manage its settings, and adjust its filters and columns, among other things. These permissions are not given by default to project administrators.
정답:
Explanation:
Components:
Users should use components when they want to auto-assign an issue to a specific user. An issue can have more than one component. Project administrators have the proper access to manage the project component. Since components only belong to a Jira project, users cannot share the component globally with other Jira projects.
Custom fields:
Users should use custom fields if they want the field to be used globally. The custom field has a few field types that can only accept a single value. Jira administrators have global permission to manage the custom field.
정답:
Explanation:
Actions are the doers of your rule. They allow you to automate tasks and make changes within your site and can perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks.
정답:
Explanation:
To complete a sprint, the user typically needs to have the 'Manage Sprints' permission in order to close the sprint itself. 'Browse Projects' permission is necessary to see the issues in the project, and the 'Transition Issues' permission is needed to move unresolved issues from the current sprint to the backlog or next sprint. The 'Edit Issues', 'Schedule Issues', and 'Move Issues' permissions are not strictly necessary to complete a sprint.
정답:
Explanation:
When a version is archived in Jira, it essentially hides that version in various planning tools and reports. However, issues that belong to the archived version can still be found and viewed via JQL search. Also, once a version is archived, issues can't be moved directly to it nor can it be released. Archiving is generally used to clean up completed or discarded work, it's a kind of soft delete where the data remains accessible if needed.