Your project is configured as follows:
* several issue types, components and versions
* a single, simple unique workflow - OPEN --> IN PROGRESS --> DONE
* Fix Version(s) can be set on the transition to IN PROGRESS
* Component(s) are required and new issues are automatically assigned to component leads
* all component leads are members of the Administrators project role
Now you have to implement the following requirements:
* an affected version needs to be added to the issue upon creation
* only component leads can choose or add a fix version when the issue is transitioned to IN PROGRESS What two configurations are prerequisites to meet the requirements? (Choose two.)

• A.Add a condition limiting execution to the Administrators role to the IN PROGRESS transition and require Fix Version/s to be set.
• B.Ensure that only members of the Administrators project role have Resolve Issues permission.
• C.Ensure Affects Versions/s is required in the used field configurations and on the correct screen.
• D.Ensure Component/s, Affects Versions/s, and Fix Version/s are required in the used field configurations.
• E.Add a condition limiting execution to the IN PROGRESS transition to the current assignee.

Comment: *

Name: *

Email: *

Verification: *

You need to configure an automation rulethat closes all the linked duplicate issues whenever a bug is closed.
Which automation rule accomplishes this?

• A.
• B.
• C.
• D.
• E.

Comment: *

Name: *

Email: *

Verification: *

Project ASTRO has two issue types that share a workflow.
You received several new requirements for the project.
Which or>e would definitelyrequire creating separate workflows for each issue type?

• A.On each issue type, a different user should be assigned after issues are transitioned to Review.
• B.On each issue type, a different security level should be set when new issues are created.
• C.On each issue type, users should see different required fields when editing.
• D.On each issue type, users should see different Resolution values when using the "Close* transition.

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

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.Create two new projects for TV and Radio.
• B.Clone the existing project and key for TV and Radio.
• C.Copy the existing permissions and notification schemes, and associate them with new projects for TV and Radio.
• D.Add TV and Radio into the existing project as components.
• E.Use issue types of Print, Radio and TV in the existing project.
• F.Create a sub-component hierarchy.

Comment: *

Name: *

Email: *

Verification: *