Managing projects
15 min
Advanced
This lesson contains exam hints about managing projects. You will also explore sandbox challenges to give you a hands-on experience to prepare you for various kinds of scenario-based questions in the exam.
Exam details
Keep these hints in mind as you prepare for your exam. They cover essential areas that will guide you while you tackle the questions effectively and will help you navigate the exam with confidence.
👇 Click the boxes below to explore the exam hints.
Sandbox challenges
To pass the exam, technical knowledge of Managing Jira projects 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 working with issues, auto-assignments, project roles and permissions, updating the issue layout and creating and managing versions. They will help to develop your approach and prompt you to investigate different methods and solutions as you prepare for the exam.
Work with issues
In this challenge, you will create and work with issues in a company-managed project.
- Create a Task and add at least two Sub-tasks.
- Add labels to the issues, including the same word in different (lower or upper) case.
- Add an attachment in the Description field to any issue.
- Note the places the attachment appears on the issue.
- Add an original time estimate to a Task and its Sub-tasks.
- Log work on the Task and its Sub-tasks.
- View how the Time Tracking field displays information on the Task, with and without the Sub-tasks, for both time spent and remaining estimate.
- Create another Task and link it to another issue.
- View how the links are shown on each issue.
- Move a Sub-task to a new parent Task.
- Create an Epic.
- Create child Tasks in the Epic.
- Note how the relationship is displayed on the Epic and the Task.
- Add values to the Report Name and Color custom fields for some of the issues.
- Transition a couple of issues.
- Mention the another user in a comment.
- Check the email of that user to see the comment and the link to the issue.
Auto-assignments
In this challenge, you will experiment with how issues are auto-assigned. Note: When creating new issues in this challenge, leave the Assignee as automatic. Complete this challenge in a company-managed project.
- Update the project settings to make the project lead the default assignee.
- Create a new issue (before components are created or added) to view automatic assignment using the project’s default assignee.
- Create components.
- Create one component with the project lead as the default assignee.
- Create one component with yourself, as the component lead and default assignee. (This should be a different user than the project lead.)
- Change the project default to be Unassigned and Create one component with the project default as the default assignee.
- Create issues using each of the components, one at a time, to view the auto-assignment. What were the results, and why?
- Create an issue with all the components to view the auto-assignment. What was the result, and why?
Project roles and permissions
In this challenge, you will experiment with the project roles that were created during the environment setup - Managers and Developers.
👇 The permission scheme for the project should have these settings.
If you are missing the project roles, permission scheme changes, or Due date field, revisit the environment setup instructions.
- Make sure that you (the user you have currently logged in as) do not have the Developers project role.
- Open an issue and attempt to update the issue’s reporter. What was the result, and why?
- Update project roles to add yourself to the Developers role.
- Open an issue and attempt to update the issue’s reporter. What was the result, and why?
- Make sure that you do not have the Managers project role.
- Open an issue and attempt to update the issue’s due date. What was the result, and why?
- Update project roles to add yourself to the Managers role.
- Open an issue and attempt to update the issue’s due date. What was the result, and why?
Update the issue layout
In this challenge, you will experiment with moving, adding, and hiding fields on the issue layout in a company-managed project.
To update the issue layout, navigate to Project settings, then select Issues, then Layout.
Edit the layout used for Stories, Epics, Tasks, and Sub-tasks.
- Add the Report Name field to the Description section.
- Move the location of the Color field in the Context section.
- Add the “Fix versions” field from Hide When Empty section to the Context section.
- Add the Development field to the Hidden section.
- Rearrange fields in the sections.
- Take note that the Summary and Status fields cannot be moved.
- Click on “Save changes” and look at issues in the project to see how the issues look after changing the layout.
- Did you notice that your custom fields are on the issue layout? Ensure you understand why.
Create and manage versions
In this challenge, you will experiment with creating, merging, releasing, and archiving versions in a company-managed project.
- Create four new versions in the project.
- Add the versions to issues in the project, so that each version has at least three issues.
- Transition issues to see how their status category is reflected on the Releases page for a version.
- Release a version with both resolved and unresolved issues. Note the choices for the unresolved issues.
- Release a version where all issues are resolved and archive the version.
- Merge two unreleased versions.
- Note what values are included and excluded in the “Fix versions” field after versions are released, archived, and merged.
How was this lesson?
next lesson
Automation
- Exam hints
- Sandbox challenges
- Perform bulk operations
- Create filters, a filter subscription, and a dashboard
- Create automation rules