Managing projects (25%-35%)

Question 1

You have hired Janice, a new scrum master, to join your team. She needs to be able to create and reorder sprints in your company-managed Kanban Board.

A Project Role with which permissions will enable her to meet the requirements?

Answer 1

“Manage Sprints” permission

Additional Details: Janice needs “Manage sprints” project permission. This permission allows people to create, start, and complete sprints in your project. This includes adjusting the sprint duration and goal.
This permission depends on product access to Jira Software.

Question 2

Scenario: When creating an issue the ‘PLANET’ team wants to track which planet out of 12 a specific issue relates to and they want to be able to use them for accurate reporting purposes in an Issue Statistics gadget.

What type of field meets these requirements?

Answer 2

“Custom field - Select List (single choice)

NOTES: The important information is that it must allow only a single planet to be chosen and that it must be used for reporting purposes in a statistics gadget.

Question 3

What are the needed permissions to be able to set due dates?

Answer 3

• Edit issues
• Schedule issues

NOTE:
Being able to edit issues is the first required permission because if you cannot edit an issue you won’t be able to modify/set its attributes.

Schedule issues permission allows people to set or modify the value of the Due date field on your project’s issues. On a company-managed Scrum or Kanban board, this permission also allows people to reorder issues (“rank”) on the board and backlog.

Question 4

If someone creates an issue with more than one component, and the default assignees for those components are different people, who will be assigned to the issue?

Answer 4

Jira assigns the issue to the default assignee of the component that is first alphabetically

(Assignee is selected > Component Lead (Component Id Ascending Order) > Project Default > Project Lead)

Question 5

TRUE or FALSE - A component default assignee will override the project’s overall default assignee.

Answer 5

TRUE

Question 6

Name the 6 global permissions

Answer 6

• Administer Jira
• Browse users and groups
• Share dashboards and filters
• Manage group filter subscriptions
• Make bulk changes
• Create team-managed projects.

Question 7

Scenario:
After a recent change, some users in your Jira Cloud site are complaining because they can no longer create team-managed projects. Yet, they are able to view and work on issues using Agile Boards.

What permissions would be preventing them from doing so?

Answer 7

Global Permission - Create team-managed projects

Question 8

What are the three types of permissions in Jira applications (They range from the high-level to granular)

Answer 8

• Global Permissions - These apply to applications as a whole, not individual projects (for example, whether users can see the other users in the application).
• Project Permissions - Organized into permission schemes, these apply to projects (e.g. who can see the project’s issues, create, edit, and assign them). While project admins can assign users to a project, they can’t customize the permission schemes for a project. There are lots of project-level permissions you can set to control what users can do within a project.
• Issue Security Permissions - Organized into security schemes, these allow the visibility of individual issues to be adjusted (within the bounds of the project’s permissions). For example, issue security permissions can let you set up types of issues that can only be seen by project admins or users in specific groups.

Question 9

Name three ways to attach images to an issue

Answer 9

• Click the “Attach” button from the issue
• Copy and Paste
• Drag & drop to the issue view

Question 10

Scenario: Nancy is a member of the company-managed project WEB3, which uses a simplified workflow generated by Jira and has never been updated since.

Nancy cannot move issues to the Done column on the project board.

Which permission does Nancy need?

Answer 10

“Transition issues” permission

NOTE: Jira Software product access is required to be able to access the Board

Question 11

What information is not displayed in the “Development” panel?

Answer 11

Pipelines

Question 12

What information is or can be displayed in the “Development” panel?

Answer 12

• Number of branches
• Number of commits and the date of the latest commit
• Number of pull requests and their statuses
• Number of builds and their statuses

Question 13

As a project administrator of a company-managed project, which actions can you perform on the issue layout? (Two)

Answer 13

• Configure a field to be hidden if it is empty
• Reorder fields

Question 14

As a project administrator of a company-managed project can you:
1. Make a field required on the issue layout?
2. Move the Resolution field to the description fields section?
3. Configure tabs?

Answer 14

NO, NO & NO

Question 15

True or False - Archived versions cannot be selected in either the “Fix Versions” field dropdown or the “Affects Versions” field dropdown

Answer 15

True - When a version is archived, it is no longer available in the Fix Versions system field nor in the Affects Versions system field.

Question 16

Scenario: Hannah is new to Jira and has just created her first team-managed project from a Kanban template. Hannah is now wondering where she can create a custom role for her newly created project, which section of the project settings can Hannah do this?

Answer 16

Access - In team-managed projects, any permission or access you want to give people in your project is controlled on the Access page. Here you can add people to your project and give them a role so they can start collaborating on your team’s work.

This page shows:
- The list of people who have access to your project
- The role they have in your project

The Access page also allows you to fine-tune the access you give to people to your team’s work. You can create roles using the “Manage roles” button to customize the permissions you grant to certain people or groups.