Atlassian ACP-100 dumps - 100% Pass Guarantee!

Your company will migrate to Jira. You plan to import with a CSV file. Which fields are required as CSV columns for your import?

A. Project

B. Project, Summary

C. Summary

D. Project, Issue Type

E. Summary, Issue Type

Your marketing company wants to evaluate Jira and purchased a 10-user license. A frequently changing group of key stakeholders ?both internal employees and external customers ?will participate in the evaluation.

If the evaluation is successful the company wants all 50 employees to start working with the tool.

You have to manage the frequently changing group of stakeholders and need to make sure only the intended users participate in the evaluation.

How should you meet these requirements?

A. Create and manage the users for stakeholders manually in the internal directory.

B. Connect Jira to your internal LDAP directory and whitelist the IPs of stakeholders.

C. Enable public signup and CAPTCHA but limit account creation to stakeholders.

D. Disable public signup and grant all project permissions to Group Anyone.

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. Create separate screens for each issue operation and issue type. Delete the Due Date field.

B. 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.

C. 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.

D. 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.

You set up a new project for a team. Soon afterward, users report that a field is missing from one of their screens. You check the screen configuration in the administration panel and you see that the field should be present.

Why can't the users see the field?

A. The changes to the screen were not published.

B. The issue operation wasn't mapped to a screen.

C. The field context does not include the project and/or issue type.

D. The users don't have permission to view that field.

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 issue type's field configuration for Component/s is not set to Required.

B. The default assignee for the issues' component is still set to Unassigned.

C. The post function Assign to Lead Developer is missing in the create transition.

D. Users creating this issue type do not have the Assign Issue permission.

E. The assignee is being set to Unassigned in the first post-function of the create transition.