Jira is the most widely used tool for agile project management and bug tracking. These Jira interview questions cover issues, workflows, boards and sprints for testers, developers and project coordinators, then JQL, dashboards, automation, permissions and administration for experienced users.
30 questions · Updated
Fundamentals, definitions and simple scenarios. Good for freshers and warm-ups.
Jira is a work management tool from Atlassian used to plan, track and release work.
Software teams use it for user stories, tasks and bugs in Scrum or Kanban; testers use it to log and track defects; and business teams use it for projects and service requests.
Jira Service Management is a separate product for IT help desks.
Common issue types are Epic (a large body of work), Story (a feature from the user's point of view), Task (work to do), Bug (a defect) and Sub-task (a smaller part of another issue).
Admins can add custom issue types.
Since 2024, Jira describes these as work items and levels in a hierarchy, with epics above stories and tasks.
A clear summary that describes the problem, the environment (build, browser, device), exact steps to reproduce, expected result and actual result, plus screenshots, videos or logs.
I set the right severity and priority, link it to the related story, and assign it according to the team's process.
A developer should be able to reproduce it without asking me questions.
Jira is used by software and business teams to plan and track work with boards, backlogs, timelines and reports.
Jira Service Management is for IT and service teams handling requests, incidents and changes through a customer portal with SLAs.
Atlassian also offers Confluence for documentation and Jira Product Discovery for collecting ideas and prioritising.
Company-managed projects are configured by Jira administrators with shared schemes for workflows, fields, screens and permissions, which keeps many projects consistent. Team-managed projects are configured by the team itself with simple settings that do not affect other projects, which suits independent teams but is harder to standardise and report across.
The backlog holds prioritised work.
In refinement, the team clarifies stories, adds acceptance criteria, splits large items and estimates them.
In sprint planning, the team selects items from the top of the backlog that fit their capacity, sets a sprint goal and starts the sprint.
During the sprint, items move across the board, and unfinished items return to the backlog or move to the next sprint at the end.
Story points are relative estimates of effort, complexity and uncertainty, often using Fibonacci-like numbers (1, 2, 3, 5, 8, 13), rather than hours.
Teams compare new work with previous stories and agree through planning poker.
Velocity, the average points completed per sprint, helps forecast how much the team can take on.
Points should not be compared between teams.
Components group issues by part of the product, such as payments or mobile app, and can assign a default lead.
Labels are free-form tags for flexible grouping, such as tech-debt.
Fix versions record which release an issue will be or was delivered in, which drives release reports and release notes.
Using them consistently makes searching and reporting reliable.
Issue links connect related work with link types such as blocks and is blocked by, relates to, duplicates, and clones.
They show dependencies between teams and help explain why work cannot start.
Issues can also be linked to Confluence pages, web links and development work such as branches and pull requests.
Run a search with the basic search fields or JQL, then save it as a filter with a name.
Saved filters can be shared with users, groups or projects, used as the basis for boards and dashboard gadgets, and subscribed to so results arrive by email on a schedule.
Favourite filters appear in the Filters menu for quick access.
Confluence pages such as requirements, design documents and meeting notes can be linked to Jira issues, and Jira issues or filter results can be embedded in Confluence pages, staying up to date. You can create Jira issues directly from Confluence text, and release notes and retrospective pages can pull in Jira data.
Applied problems, trade-offs and questions about your own projects.
A workflow is the set of statuses an issue moves through and the transitions between them, such as To Do, In Progress, In Review, In Testing and Done.
Transitions can have conditions (who can move it), validators (required fields) and post functions (such as assigning the issue or updating a field).
Different issue types can use different workflows.
A Scrum board works in time-boxed sprints planned from a backlog, with sprint goals, story points, and reports such as burndown charts and velocity. A Kanban board is a continuous flow without sprints, with work-in-progress limits on columns to prevent overload, and reports such as the cumulative flow diagram and control chart for cycle time.
Severity is how badly the bug affects the system, set mostly by the tester, for example a crash is critical while a typo is low.
Priority is how soon it should be fixed, set by the product owner or manager based on business impact.
A spelling mistake in the company name on the home page is low severity but high priority.
Jira Query Language is used to search issues precisely.
Examples: project = APP AND type = Bug AND status != Done finds open bugs; assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC shows my open work; created >= -7d finds issues from the last week; and sprint in openSprints() lists the current sprint.
Saved JQL filters power dashboards and boards.
Versions represent releases with start and release dates.
Issues are assigned to versions through the fix version field, and the release hub shows progress, unresolved issues and linked development and deployment information.
When a version is released, unfinished issues can be moved to the next version, and release notes can be generated from the issues included.
Epics group stories and tasks into larger pieces of work, such as a feature or project. The timeline (roadmap) view shows epics and their child issues across dates with dependencies, and Advanced Planning (Plans) in Premium plans across several teams and projects, with capacity, releases and scenario planning, which helps managers see delivery dates and risks.
Custom fields add data that Jira does not track by default, such as customer name or environment, with types such as select lists, dates and user pickers.
Field configurations make fields required or hidden, and screens decide which fields appear when creating, editing or transitioning issues.
Too many custom fields slow Jira and confuse users, so they are added carefully.
Jira treats an issue as resolved only when the resolution field has a value, such as Done, Won't Do or Duplicate, not just when its status is Done.
Reports, filters such as resolution = Unresolved, and dashboards rely on it.
Workflows should set the resolution when moving to a final status and clear it when an issue is reopened.
The velocity chart shows committed versus completed story points per sprint, and a stable average helps forecast future sprints.
The burndown chart shows remaining work during a sprint against an ideal line: a flat line means work is not being completed or is not being updated, and a rising line shows scope being added.
They are tools for conversation, not for judging individuals.
Jira does not manage tests natively, so teams use apps such as Xray or Zephyr. They add test, test plan, test set and test execution issue types, link tests to requirements and defects for traceability, record execution results, and import automated test results from CI pipelines, giving coverage and execution reports inside Jira.
Connecting a Git tool links commits, branches, pull requests, builds and deployments to issues when the issue key, such as APP-123, appears in branch names, commit messages or pull request titles.
The development panel shows this on the issue.
Smart commits let developers comment, log time or transition issues from commit messages, and automation can move issues when pull requests merge.
System design, deep internals, leadership and tough follow-ups.
I create saved filters with JQL and build dashboards with gadgets such as filter results, pie charts by status or priority, created vs resolved charts, sprint health and two-dimensional statistics.
Scrum reports like velocity and burndown show delivery trends.
I share dashboards with the right permissions and keep them focused on the questions stakeholders actually ask.
Jira Automation runs rules made of a trigger, conditions and actions without code.
Examples: when all sub-tasks are done, move the parent to Done; when a bug is created with Critical priority, notify the team in Slack and assign the on-call engineer; when a pull request is merged, transition the issue; or every Monday, comment on stale issues.
It reduces manual updates and keeps data consistent.
Jira projects are configured through schemes that can be shared: permission schemes (who can browse, create, edit or transition issues), notification schemes, workflow schemes, issue type schemes and field configurations. I assign permissions to project roles and groups rather than individual users, keep schemes shared across similar projects to reduce maintenance, and use issue security levels for sensitive issues.
Customers submit requests through a portal, email or chat, choosing request types with tailored forms.
Agents work from queues, with SLAs tracking response and resolution times, a knowledge base in Confluence suggesting articles, and approvals for requests such as access changes.
It supports ITSM practices including incident, problem, change and asset management, with on-call alerting.
Standardise workflows, issue types and fields through shared schemes, use a clear hierarchy (initiatives, epics, stories and sub-tasks), use Plans for cross-team planning and dependencies, and align with frameworks such as SAFe where used. Agree conventions for components, labels and versions so cross-project reports work, and give teams some flexibility within those standards.
Regularly remove unused custom fields, schemes, workflows and statuses, share configuration between similar projects, archive old projects, review permissions and groups, limit global automation rules that run often, monitor performance, keep apps updated and remove unused ones, and document configuration decisions. A change request process stops uncontrolled growth.
The Jira REST API creates, updates and searches issues using JQL, with API tokens or OAuth, and webhooks notify other systems when issues are created or changed.
Jira Automation can send web requests to external services, and Atlassian Forge apps extend Jira with custom functionality.
Common integrations include CI/CD tools, Slack or Teams, monitoring tools and CRMs.
Cycle time (how long work takes from start to done), lead time (from request to delivery), throughput (items completed per week), work in progress, and flow efficiency.
The control chart shows cycle time per issue and highlights outliers, and the cumulative flow diagram shows bottlenecks where work piles up in a status.
These metrics help teams improve predictability.
See all MIS Executive interview questions, covering Advanced Excel, VBA Macros, Google Sheets, Power BI, Tableau and more.