Unlock hundreds more features
Save your Quiz to the Dashboard
View and Export Results
Use AI to Create Quizzes and Analyse Results

OR
Sign inSign in with Facebook
Sign inSign in with Google
Quizzes > Computers & IT

Jira fundamentals badge practice quiz

Quick, free Jira fundamentals practice test. Instant results and review tips.

Editorial: Review CompletedCreated By: Fredi DarmawanUpdated Aug 26, 2025
Difficulty: Moderate
2-5mins
Learning OutcomesCheat Sheet
Paper art illustration of quiz badge workflow arrows boards issue tracking icons on teal background

Use this quiz to check your skills for the Jira Fundamentals Badge and spot gaps across workflows, boards, and issue tracking. See instant results with brief explanations, and keep learning with a project management fundamentals quiz and a free scrum master practice test to round out your toolkit.

Which issue type is used to group and manage a large body of work in Jira?
Task
Epic
Story
Bug
Epics are high-level issue types used to group related stories and tasks under a larger initiative. They help in planning and tracking progress across multiple sprints. Epics can be broken down into stories and other issue types for detailed work. Learn more at .
What does Jira's "Create" button do?
Opens board settings
Deletes an existing issue
Opens the issue creation dialog
Starts a sprint
The "Create" button in Jira opens a dialog where users can enter details for a new issue, such as summary, description, and project. It's the primary way to log new work items in the system. Other actions like deleting or settings configuration require different menus. Read more at .
Which default Jira issue type is specifically used to track defects?
Bug
Story
Task
Epic
The Bug issue type is provided by default in Jira projects to capture and track software defects. It includes fields like priority and severity that help teams manage and fix issues. Using the Bug type distinguishes defects from feature requests or tasks. See details at .
On a Scrum board, what does the "Backlog" typically contain?
Issues currently in progress
Only sub-tasks
Completed issues
Future issues not yet in sprints
The Backlog on a Scrum board holds all issues that are not yet assigned to an active sprint. Teams groom this list to prioritize and break down work before sprint planning. Completed issues move out of the backlog into done or closed statuses. More information at .
What does JQL stand for in Jira?
Java Query Logic
Jira Quick Lookup
Jira Quality Logger
Jira Query Language
JQL, or Jira Query Language, is the powerful syntax used to search for issues in Jira. It allows users to create complex filters based on fields, operators, and functions. Familiarity with JQL enhances the ability to find and report on specific sets of issues. Learn more at .
Which of the following is a default project role in Jira?
Guests
Testers
Developers
Observers
Jira includes several default project roles: Administrators, Developers, and Users. The Developers role is used to grant users permissions like creating and editing issues. Custom roles like Testers or Observers are not provided out of the box. Details at .
Which feature in Jira displays issues as cards in columns that reflect workflow statuses?
Filter
Report
Dashboard
Board
Boards in Jira Software (Scrum and Kanban) display issues as cards arranged in columns representing workflow steps. They provide a visual way to track work in progress and manage flows. Dashboards and reports offer different overviews but do not show columns of cards. More at .
Which permission is required to perform a bulk change of issues in Jira?
Manage Sprints
Schedule Issues
Bulk Change Issues
Transition Issues
To carry out bulk operations on multiple issues at once, users must have the "Bulk Change Issues" permission in the project's permission scheme. Without it, the bulk change wizard is inaccessible. This permission helps control mass updates and prevent unintended edits. More info at .
What is a component in Jira?
A sub-task type
A project-specific categorization of issues
A global permission
A label for code binaries
Components are subsections within a project used to group and categorize issues logically. They help teams assign issues, generate reports, and filter work by area or subsystem. Components can also have default assignees for new issues. See details at .
How can you make a custom field available only to specific issue types?
Field configuration
Issue layout
Workflow scheme
Field context
Custom field contexts in Jira allow administrators to limit a field's availability to certain projects and issue types. By defining a context, you can control where the field appears and what options it shows. Field configurations control behavior (e.g., hidden or required), not scope. Learn how at .
Which default role is typically assigned the "Browse Projects" permission?
Developers
Anonymous
Administrators
Users
The default "Users" role is granted the "Browse Projects" permission so that assigned users can view issues and project settings. Administrators have broader access, while Developers focus on issue operations. Anonymous users have limited or no access unless specifically enabled. Details at .
What does the Resolution field in an issue indicate?
Why the issue was closed
The status of the issue
When the issue was created
Who resolved the issue
The Resolution field captures the reason or outcome when an issue is closed, such as "Fixed" or "Won't Fix." It differentiates closed issues from those merely in a closed status without a resolution. A resolution must be set for proper reporting. Read more at .
Which Jira feature allows you to follow changes on a filter and receive email updates?
Webhooks
Dashboard gadgets
Filter subscriptions
Email notifications
Filter subscriptions let users schedule automatic emails containing current results of a saved filter at regular intervals. This keeps stakeholders informed without manual checks. Email notifications handle issue-level events, not filter summaries. Learn how at .
Which issue link type indicates that one issue is preventing another from progressing?
Blocks
Duplicates
Clones
Relates to
The "Blocks" link type signifies that the source issue is preventing the target issue from moving forward. It's useful for visualizing dependencies. Conversely, "Is blocked by" indicates the issue is waiting on another. See linking at .
True or False: JQL supports using functions like currentUser().
True
False
JQL includes functions such as currentUser(), now(), and startOfMonth() to create dynamic queries. Using currentUser() allows filters to return issues relevant to the logged-in user. This makes dashboards and boards more personalized. More examples at .
Which REST API endpoint would you use to fetch issue details?
/rest/api/2/issue/{issueIdOrKey}
/rest/api/2/project/{projectId}
/rest/api/2/search
/rest/agile/1.0/issue/{issueIdOrKey}
The endpoint /rest/api/2/issue/{issueIdOrKey} returns full details for a specified issue. It's part of Jira's core REST API. The agile endpoint and search endpoint are used for board data and multiple-issue queries, respectively. See API docs at .
What does a Field Configuration Scheme allow you to do?
Define workflows for issue transitions
Create custom dashboard layouts
Map multiple field configurations to different issue types
Assign a single field configuration to one project only
A Field Configuration Scheme associates different field configurations with issue types within a project. This lets you enforce varied field behaviors (required, hidden, read-only) for each issue type. It decouples field settings from project-level schemes. Learn more at .
How can you restrict a workflow transition to certain users or groups?
Field configuration
Permission scheme
Transition property
Workflow condition
Workflow conditions control which users or groups can execute a specific transition. By adding conditions like "User Is In Project Role", you limit transitions to eligible users. Transition properties control field behavior, not access. Read more at .
In Jira Software, how do you start a new sprint?
Create a new board
Click the "Start sprint" button in the backlog view
Move issues to 'In Progress' status
Publish the backlog
To begin a sprint, open your Scrum board's backlog and click the "Start sprint" button. You can then set sprint duration and goals before launch. Simply moving issues between statuses does not initiate a sprint. More at .
Which Jira gadget would you use to show the progress of issues over time on a dashboard?
Pie Chart
Filter Results
Average Age Chart
Created vs Resolved Chart
The Created vs Resolved Chart gadget plots the number of issues created against those resolved over a selected time period. It helps teams monitor whether they are clearing work as quickly as new items are added. Pie Charts and other gadgets serve different purposes. See gadget options at .
Which Jira feature allows you to hide a custom field from screens?
Field configuration
Screen scheme
Workflow scheme
Field context
Field configurations let administrators set fields to Hidden, Required, or Optional for issues in a project. By marking a field as Hidden, it will not appear on any screens. Field contexts control value scope, not visibility. More at .
How can you ensure that attachments added to an issue are only visible to certain roles?
Notification scheme
Project role
Issue security level
Permission scheme
Issue security levels let you restrict visibility of an issue and its attachments to certain roles or groups. By defining security schemes, only authorized users can view sensitive content. Permission and notification schemes control other aspects but not per-issue visibility. Learn more at .
True or False: You can have multiple active sprints in the same Scrum board simultaneously.
True
False
Jira Software permits only one active sprint at a time per Scrum board. Attempting to start another sprint will prompt you to complete or close the existing one first. This enforces focused delivery and consistent reporting. Read more at .
Which JQL query finds issues not updated in the last two weeks?
updated = -2w
updated >= -2w
updated > -2w
updated <= -2w
In JQL, using 'updated <= -2w' returns issues whose last update occurred two or more weeks ago. The '<=' operator ensures you capture everything older than the specified function. Other operators will invert the logic or require exact matches. See advanced JQL at .
Which Jira REST API endpoint do you use to create a new sprint under a specific board?
/rest/api/2/sprint
/rest/agile/1.0/board/{boardId}/sprint
/rest/api/2/board/{boardId}/sprint
/rest/agile/1.0/sprint
To create a sprint via the Jira Agile REST API, you POST to /rest/agile/1.0/sprint, including the boardId in the request body. The /rest/api/2 namespace does not support agile-specific operations. Details and examples at .
0
{"name":"Which issue type is used to group and manage a large body of work in Jira?", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Which issue type is used to group and manage a large body of work in Jira?, What does Jira's \"Create\" button do?, Which default Jira issue type is specifically used to track defects?","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}

Study Outcomes

  1. Analyze Jira workflows -

    Evaluate common workflow schemes and transitions to streamline project processes and mirror real-world scenarios.

  2. Configure Scrum and Kanban boards -

    Set up and customize board columns, filters, and swimlanes to reflect team needs and optimize sprint planning.

  3. Apply issue tracking best practices -

    Use issue types, statuses, priorities, and custom fields to manage tasks, bugs, and feature requests effectively.

  4. Interpret reports and dashboards -

    Read, customize, and analyze Jira charts and gadgets to monitor progress, performance, and team workload.

  5. Evaluate readiness for the Jira Fundamentals Badge -

    Assess your knowledge gaps using quiz-style questions that mirror the Jira certification practice test format.

  6. Plan targeted exam preparation -

    Identify areas for improvement and leverage jira exam practice questions to boost confidence before taking the quiz online.

Cheat Sheet

  1. Jira Workflows and Transitions -

    Understanding statuses, transitions, and resolutions is essential for the jira fundamentals badge. Consult Atlassian University (university.atlassian.com) for official workflow templates and best practices. Use the mnemonic "TITLe Do" (To Do → In Progress → Testing → Live → Done) to lock in key steps.

  2. Scrum vs. Kanban Boards -

    Master the differences between Scrum boards (with time-boxed sprints) and Kanban boards (with continuous flow) by exploring the official Atlassian documentation. Try a jira fundamentals quiz online to see boards in action by setting up swimlanes, WIP limits, and backlog grooming. Tip: "Scrum Sprints Stop; Kanban Continues" helps you remember discrete versus continuous workflows.

  3. Issue Types and Field Configurations -

    Know default issue types (Epic, Story, Task, Bug) and how custom types affect screens and workflows, as detailed on Atlassian's website. The mnemonic "Every Superhero Tackles Battles" can help you recall Epic, Story, Task, Bug. Practice with jira exam practice questions to configure screens, custom fields, and mandatory fields correctly.

  4. Advanced JQL for Effective Filtering -

    Advanced Jira Query Language (JQL) lets you craft precise filters; start with assignee = currentUser() AND status != Done (source: Atlassian Developer). Use boolean operators (AND, OR, NOT) and functions (e.g., ORDER BY priority DESC) to refine searches. Sharpen skills with a free jira certification quiz focusing on JQL scenarios.

  5. Permission Schemes and Security -

    Project roles, permission schemes, and issue-level security define who can view or edit issues (see Atlassian Support). Remember "ROXX" (Reporter, Owner, Examiner, X) to map permissions to roles. Include a jira certification practice test in your study plan to test scheme configurations and user-management scenarios.

Make a Quiz (FREE) Copy & Edit This Quiz Create a Quiz with AI

Programming & Software Quizzes

Powered by: Quiz Maker