MANAGING PROJECTS

1. Who is responsible for configuring the Jira instance for all users?
R. Jira Administrator. They, in general, know the most about the technical capabilities
of Jira and can set policies for the entire company to use with their Jira projects. The
changes that they can make can affect multiple projects, so they must be very
knowledgeable of Jira.

2. What are project templates for the Software project type?

R. Scrum, Bug and Kanban.

3. Which of the following is true?

R.
a. Any Jira user can create and configure a project.
b. Project administrators need to work with Jira administrators to create and fully
configure projects.
c. Site administrators are the only users who can create projects.
d. Project administrator have all the necessary permissions to create and fully configure
projects independently.

Jira administrators are the only users who can create projects and perform higher level
configurations. Project administrators can perform certain basic project configurations,
and are responsible for maintaining projects.
 MANAGING ROLES & PERMISSIONS

4. Match the administrator to their responsibilities.

5. Match the term to its correct definition.

6. True or false? Global permissions grant capabilities across a Jira instance.

R. True. Global permissions allow Jira administrators to control functionality that is
system-wide and project-independent.
7. “Certain team members need to be able to delete issues, which normally only
administrators can do. But, we don’t want to give full administrator permissions
to these team members; they only need to be able to delete issues”
R.
a. Jira Admin creates a custom project role (Ex: Issue Managers)
b. Jira Admin creates a new permission scheme (Ex: Development Permission Scheme).
c. Jira Admin assigns the Delete issues permission to the custom role.
d. Jira Admin associates the Development Permission Scheme with the project.
e. Project Admin adds selected project users to the Issue Managers custom role.

8. “For certain projects, we need specific users to be able to start and stop sprints. By
default, any Jira Software user can star/stop sprints. How can we allow only
selected users to manage sprints?”
R.
a. Jira Admin creates a custom project role (Ex: Scrum Master)
b. Jira Admin creates a new permission scheme (Ex: Development Permission Scheme)
c. Jira Admin updates the Manage sprints permission, so it only applies to the Scrum
Master custom role.
d. Jira Admin associates the Development Permission Scheme with the project.
e. Project Admin adds selected project users to the Scrum Master custom role.

9. When a user is added to a project’s Administrator role, what do they become?

R. Project Administrator for that project. Project roles are specific to individual projects.
A user may be a Project administrator in Project A and a regular team member in Project
B.

10. How do Project administrators manage permissions within a project?

R. Add users to project roles. Project administrators are not able to manipulate individual
permission settings. Instead, they can grant permissions to users by adding those users
to project roles, that in turn, are associated with specific permissions.
 MANAGING BOARDS

11. “We want to apply different statuses to issues moved to a Review column. When
users move an issue into the Review column, they need to set the status to either
New or Revised”.
R.
a. Project Admin adds a Review column to the board.
b. Project Admin creates two new workflow statuses: New and Revised.
c. Project Admin adds two new statuses to the Review column.

12. “Code review is an important part of the software development process. I want to
add a specific status called “In Code Review”, so it’s clear to my team wich issues
are under active development and wich issues are awaiting review”.
R. Reviewing code is distinctly different than writing code, so it makes sense to add a
new status.

13. “I want to add new status called Failed Verification for all issues that don’t pass
review by my team”
R. We’d advise against doing this as the test engineers can simply send any issue that
fails review back to a previous state, such as In Development.

14. True or false? A single board column can be associated with any number of
statuses.
R. True. A single board column can be associated with multiple statuses, not just one.

15. “Our Kanban Done column is getting overloaded! How can we clean up completed
issues from a Kanban board?”
R. Kanban boards are structured for continuos work. As tasks move through the board,
they eventually land in the Done column, where they can accumulate and clutter up the
board. Let’s explore four approaches:
a. Configure a date-based Kanban board.
b. Modify the board’s filter to hide older, resolved issues.
c. Create a filter to hide older resolved issues that users can apply.
d. Use Jira’s versions and releases feature to clear groups of issues.

16. What does a board sub-filter do?

R. Filters the results of the board’s filter query. The sub-filter is applied to the results of
the board’s filter query.
 BOARDS & PROJECTS

17. A new project is created with an initial Scrum board. Which of the following is
true?
R. Kanban boards can be added to the project (TRUE)
The project’s initial board cannot reference other projects (FALSE)
The initial board’s sub-filter can be edited to refine what the board displays (FALSE)

MANAGING ISSUES

18. ” An _________ represents an element of work that needs to be done. That work
can be a task, a bug, a feature request, or any type of work item pertaining to your
organization. _________ contain descriptive metadata and relevant information
about that work item. _________ visually indicate the current state of each work
item.”
R. issue, fields, boards.

19. “We want to change how we use issue types. We want to track feature requests
separate from bugs, replace Task with Engineering Task, and use Story as the
default issue type”
R. To satisfy the business requirement, the Jira Administrator would:
a. Create a new Feature Request and Engineering Task issue types in the new standard
project.
b. Change the order to issue types in the Issue type scheme.
c. Change the order of issue types and set the default issue type to Story in the DEV:
Scrum Issue Type Scheme (the issue type scheme for the new standard project).

20. “My team would like to organize the work in our project by certain criteria to
make it easier for tracking and reporting: product feature, geographic location,
and business unit”
R. Component group project tasks into smaller sub-sections specific to a single project.
Component can represent anything: platform, location, function, content type, and more.
21. “We want to transfer issues from one project to another without losing any data
associated with the issues. We have multiple projects, each with custom Issue Types
and custom fields”.
R. Use a Bulk change.
a. Use advance issue search (need Make bulk changes global permission).
b. Choose an operation (need Move issue project permission).
c. Map statuses and issue types.
d. Update fields for the target project.
e. Confirm the move.

22. You want to reduce the potencial for errors and typos, so you don¡t want to use
labels. What could you use instead?
R. Components and Custom fields. Both of these options provide limit free-form value
entry, thereby minimizing erroneous tagging of issues.

AUTOMATION

23. “I want to automatically create a set of subtasks related to posting a blog when a
new Task issue is created”
R.
a. Select a trigger: Issue created.
b. Select conditions: Issue fields condition for Issue type field.
c. Select actions: Create subtasks action.
d. Name the rule and turn in on.
e. Test the rule.
f. Check the audit log.
24. If an automation rule has multiple conditions, the actions will execute when:
R. All of the conditions are true. If only one condition is met then the trigger isn't
meeting all the requirements from the role to process to the action.
 REPORTS & DASHBOARDS

25. Wich charts focuses on the cycle time for individual issues?
R. The control chart focuses on cycle time for individual issues.

26. .
 OTHER JIRA FEATURES

27. Which of the following are reasons to choose individual projects for each
team? (Select 3)

R.

a. Sprint planning isn’t coordinated among teams

b. Teams work from dependent roadmaps (ESTA NO)
c. Releases are not coordinated between teams
d. Individual reporting and metrics are needed

28. What are the benefits of using shared project configurations (Select 2)
R.
a. Only one Project administrator for all projects (ESTA NO).
b. Promotes consistency across projects.
c. Every project uses the same board (ESTA NO).
d. Troubleshooting problems is easier.

Since multiple projects share the same configuration, projects can be managed and
maintained in a consistent manner. By sharing configurations, the number of unique
configuration objects in the system is reduced, and the ones being used are well known,
making troubleshooting less difficult.

CREATING & CONFIGURING TEAM-MANAGED PROJECT

29. Which of the following statements about team-managed projects is true?

R.
a. A user can only be assigned a single role in a project.
b. A project’s access can only be specified when the project is created.
c. If a user is assigned to the Viewer and Member roles for a project, they can add an
edit issues.

If a user is assigned multiple roles in a project, the most permissive role (Members)
wins. Members can add and edit issues.