General project configuration
10 min
In this lesson, you'll work through sandbox challenges designed to give you hands-on experience with configuring projects. These challenges will help reinforce key concepts and prepare you for various kinds of scenario-based questions in the exam.
You will also test your knowledge and assess if you're ready for the exam with these sample questions.
Sandbox challenges
To pass the exam, technical knowledge of Jira features is crucial, but it is not enough. The majority of exam questions are based on scenarios that must be understood, analyzed, and evaluated to find the correct answer that fits the stated constraints.
The following challenges will assist you in exploring scenarios with issue assignment, creating projects and merging and splitting projects. They will help to develop your approach and prompt you to investigate different methods and solutions as you prepare for the exam.
Issue assignment
The Assignee field is very important in Jira so that each issue has a single designated person responsible for the progress of work and serves as a clear point of contact.
- Experiment with assigning issues manually and automatically.
- Configure auto-assignment using components.
- In what order does Jira process auto-assignment (e.g., Project Default, component Default Assignee, manual selection)?
- How can mailed-in issues be auto-assigned?
- How can you bypass auto-assignment?
- How can you assign issues via workflow post-functions in a company-managed project?
- How can you assign issues via workflow rules in a team-managed project?
- How can you assign issues via automation rules?
- What is the difference between “Assign Issues” and “Assignable User” permissions?
Create projects
You received business requirements to create a new project.
- What are the considerations for choosing a team-managed versus a company-managed project?
- What do you need to know in order to choose a particular project template?
- What are the pros and cons of creating a company-managed project using a shared configuration?
- How should you decide whether to use components, labels, or custom fields to sub-categorize issues within the project?
- What can project administrators do in a company-managed project?
- What can project administrators do in a team-managed project?
Merge and split projects
Two projects need to be merged.
- What must you assess before continuing with the migration and how can you merge the projects?
- Is the process different if they have different project types (e.g. software and business)?
- Is the process different if one is a company-managed project and the other is a team-managed project?
- What data is preserved and what data is lost?
- What common errors do you encounter when using bulk operations to migrate issues between projects?
Split projects
Alpha software team and their project are splitting in two. The new project and team will be called Bravo.
- What requirements would necessitate creating separate individual schemes versus using shared schemes in company-managed projects?
- What requirements would necessitate creating a separate workflow for one or all of the issue types?
- Can both teams use the same custom fields with different values and defaults in each project?
- How can you satisfy the need for different sets of resolutions in company-managed projects?
- How do the above changes affect reporting?
Resources for these sample questions
For more information on the features described in these sample questions, refer to these resources.