Test your Jira knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is an "Epic" in Jira, and how does it relate to smaller issues like Stories or Tasks?
In this round
What is an "Epic" in Jira, and how does it relate to smaller issues like Stories or Tasks?
What is a "swimlane" on a Jira board, and what organizational purpose does it serve?
What is a "story point" in Jira, and what does it typically represent in agile estimation?
What is a general reason a software team might invest time in configuring Jira workflows, fields, and processes carefully, rather than just using Jira's most basic, default configuration?
What is the general purpose of linking issues together in Jira (e.g. marking one issue as "blocked by" another, or "relates to" another)?
What is "velocity" in the context of Scrum-based Jira usage, and how is it typically used for future sprint planning?
What is a "backlog" in Jira, and what role does it play in agile planning?
What is a "custom field" in Jira, and why might a team configure one beyond Jira's default fields (like summary, description, assignee)?
What is a "burndown chart" in Jira, and what does it visualize for a sprint in progress?
What is an "issue" in Jira, and what are some common issue types a software team might use?
What is a general reason a team might integrate Jira with their version control system (like linking Jira issues to GitHub/GitLab commits and pull requests)?
What is a "sprint" in Jira (when used to support Scrum-based agile development), and what does it represent?