Jira Interview Questions and Answers: From Basics to Admin and Scenarios
If you’re preparing for Jira interview questions, the good news is that most interviewers stick to a predictable set: how issues, workflows, boards, and sprints fit together; how you’d query data with JQL; how permissions and schemes work; and how you’d handle a messy real-world situation like merging two instances or recovering deleted work. What changes by role is the depth.
A QA tester gets defect-tracking questions, a Scrum Master gets sprint and reporting questions, and a Jira admin gets schemes, permissions, and migration questions.
This guide covers each group, with answers short enough to say out loud, JQL examples you can write on a whiteboard, and scenario answers that show how you think.
It also covers what’s changed recently in Jira Cloud, because interviewers increasingly ask about it.
What’s current in 2026
A few facts to have ready:
- Terminology is shifting. Jira Cloud’s release notes now say “work items” where older material says “issues.” Say “issues (now called work items in Jira Cloud)” and you cover both.
- AI is built in. Atlassian’s Rovo powers AI features across Jira, Confluence, and Jira Service Management. Recent release notes mention AI-powered JQL error fixing (generally available as of early 2026), bulk selection of up to 1,000 work items, and “Agents in Jira” reaching general availability in June 2026. Atlassian’s Rovo MCP server also lets AI tools and agents read and work with Jira data such as boards, sprints, comments, and worklogs.
- Data Center is being retired. Atlassian stopped selling Data Center to new customers on March 30, 2026, froze new Data Center features, and set the final end of life for March 28, 2029, when Data Center products become read-only. Expect migration questions if the employer still runs Data Center.
Basic Jira questions
1. What is Jira?
Atlassian’s tool for planning, tracking, and managing work. Teams use it for software development, bug tracking, agile project management, IT service desks, and general task tracking.
2. What are the main Jira products?
Jira (the core work-management and software product), Jira Service Management for support and IT service desks, and Jira Product Discovery for capturing and prioritizing ideas. Older material also mentions “Jira Core” and “Jira Work Management,” which have been folded into Jira.
3. What is an issue (work item)?
The basic unit of work: a task, bug, story, epic, or any custom type you define. Each has fields such as summary, description, assignee, priority, status, and labels.
4. What are the standard issue types and hierarchy?
Epic (a large body of work), Story or Task or Bug (the standard level), and Sub-task (a piece of a parent issue). Higher levels such as Initiative can sit above epics in plans, depending on your plan and configuration.
5. What’s the difference between team-managed and company-managed projects?
Team-managed projects are configured by the team inside the project, so they’re simple and independent. Company-managed projects use shared configuration (schemes) controlled by admins, which suits organizations that need consistency across many projects.
6. What is a workflow?
The path an issue follows from creation to resolution: statuses (like To Do, In Progress, Done) connected by transitions. In company-managed projects, transitions can have conditions (who can use it), validators (check input before it proceeds), and post functions (actions that run afterward).
7. What’s the difference between a status and a resolution?
Status shows where an issue is in the workflow. Resolution records how it was closed (Done, Won’t Do, Duplicate). An issue with an empty resolution is considered unresolved.
8. What are components, versions, and labels?
Components group issues within a project (like “Payments” or “API”), versions track releases (fix version and affects version), and labels are free-form tags for flexible searching.
9. What is the difference between priority and severity?
Priority reflects business urgency, which is how soon it should be fixed. Severity reflects technical impact, which is how badly it breaks things. Jira ships a priority field, and many teams add a custom severity field.
Agile questions
10. Scrum vs Kanban boards in Jira?
Scrum boards organize work into time-boxed sprints with a backlog, sprint planning, and reports like burndown and velocity. Kanban boards show continuous flow with columns and optional WIP (work-in-progress) limits, and use reports like the cumulative flow diagram and control chart.
11. What is a sprint, and how do you run one in Jira?
A fixed-length iteration. You groom the backlog, plan the sprint by dragging issues in, start it, track progress on the board, and complete it. Unfinished items return to the backlog or move to the next sprint.
12. What are story points?
A relative estimate of effort and complexity, not hours. Teams add them up per sprint to measure velocity and plan capacity.
13. What’s a burndown chart? What’s a velocity chart?
A burndown chart shows remaining work against time in a sprint, so you can see if the team is on track. A velocity chart shows how much work was completed in past sprints, which helps forecast future capacity.
14. How do you manage the backlog?
Keep it prioritized by value, refine items before planning (clear acceptance criteria, estimates), split large items, and remove stale ones. A healthy backlog is ordered, not just long.
15. What do the time-tracking colors mean?
Blue is the original estimate, orange is the remaining estimate, and green is the time logged.
JQL questions
16. What is JQL?
Jira Query Language, a structured way to search issues. A query is made of fields, operators, values, and keywords like AND, OR, and ORDER BY. Saved queries become filters, which power boards, dashboards, and subscriptions.
17. Write a few JQL queries.
# My open work, highest priority first
assignee = currentUser() AND statusCategory != Done ORDER BY priority DESC
# Bugs created in the last 7 days in project APP
project = APP AND issuetype = Bug AND created >= -7d
# Everything in active sprints that is in progress
sprint in openSprints() AND status = “In Progress”
# Unassigned items in the backlog
project = APP AND assignee is EMPTY AND status = “To Do”
# Overdue and unresolved
resolution = Unresolved AND duedate < now()
Common functions to mention: currentUser(), openSprints(), startOfWeek(), and membersOf(“group”).
18. What’s the difference between a filter and a dashboard?
A filter is a saved JQL search. A dashboard is a page of gadgets (charts, lists, counts) that often use filters as their data source.
Configuration and admin questions
19. What are schemes in Jira (company-managed)?
Reusable sets of configuration applied to projects: issue type scheme, workflow scheme, screen scheme, field configuration scheme, permission scheme, and notification scheme.
20. How do permission schemes work?
A permission scheme defines who can do what in a project (create issues, edit, transition, administer), and grants permissions to users, groups, or project roles. Global permissions apply across the whole site, such as who can administer Jira.
21. What are project roles?
A flexible way to grant access, like Developers or Administrators, mapped to people per project, so the same permission scheme can serve many projects with different members.
22. How do you create a custom field?
Go to Jira settings, then Issues, then Custom fields, create the field, choose its type (text, select, date, user), set its context (which projects and issue types), and add it to the relevant screens. Skipping the screen step is the classic reason a new field doesn’t appear.
23. What are notification schemes and issue security levels?
Notification schemes decide who gets emailed for which events. Issue security levels restrict who can view specific issues, which suits sensitive items such as HR or security work.
24. What is bulk change?
Editing many issues at once (transition, reassign, move, add labels, edit fields). Recent Jira Cloud releases let you select up to 1,000 work items matching a filter in one click. You can also avoid notification floods when doing it.
25. Clone vs move vs link?
Cloning creates a copy that links back to the original. Moving changes an issue’s project or type. Linking connects issues with relationships such as “blocks” or “relates to,” without copying anything.
Automation and integrations
26. How does Jira Automation work?
A rule has a trigger (an event or schedule), optional conditions, and actions. For example: when an issue moves to Done, if all of the epic’s children are done, then transition the epic and notify the owner.
27. What integrations do you use?
Confluence for documentation, Bitbucket or GitHub for linking commits and pull requests to issues, CI/CD tools for build status, Slack or Teams for notifications, and test-management apps for QA workflows.
28. How can AI help in Jira?
Rovo-based features can summarize comment threads, draft work item descriptions, generate JQL or automation rules from plain-language prompts, and run agents that act on items. A good answer adds that you’d review AI output instead of trusting it blindly, and that site admins control whether AI features are on.
Jira for testers and service desks
29. How do you track defects in Jira?
Create Bug issues with clear steps to reproduce, expected and actual results, environment, severity, and attachments. Link them to the story or test case, track them through a workflow (Open, In Progress, Fixed, Verified, Closed), and report with dashboards.
30. How do you manage test cycles?
Jira itself isn’t a test management tool, so teams often add an app such as Xray or Zephyr to organize test cases and executions, or model tests as issues with links.
31. How does Jira Service Management work?
Customers submit requests through a portal or email, agents handle them in queues, and SLAs track response and resolution targets. Requests can link to Jira Software issues when a fix needs engineering.
Scenario questions
32. Two teams use separate Jira instances, and you must merge them. How?
Audit both instances (projects, workflows, fields, users, apps), decide the target standard, clean up before moving, test the migration on a staging copy, map users and custom fields, migrate in phases, and communicate the cutover plan. Backups come first.
33. Someone deleted important issues. What now?
Check the audit log to confirm what happened, restore from a recent backup if available (on Cloud this may involve Atlassian support or your own scheduled backups), and review permissions so delete rights aren’t broad. Then add a policy: restrict the delete permission and use a “Cancelled” status instead.
34. Jira is slow for a large team. What do you check?
Heavy or inefficient filters and dashboards, too many custom fields and automations, large boards, marketplace apps, and, on self-hosted setups, hardware, indexing, and database health. Use admin tools to find expensive queries.
35. Different teams want different workflows. How do you balance that?
Offer a small set of standard workflows, allow limited variation where it truly matters, and use team-managed projects for autonomy where cross-project reporting isn’t needed. Too many workflows make reporting and maintenance painful.
36. How would you report progress to executives?
Pick a few outcome-focused measures, such as epic or initiative progress, release readiness, cycle time, and blocked work. Build a dashboard or roadmap view with saved filters, and add context in plain language instead of dumping charts.
37. We run Jira Data Center. What’s your advice?
Plan the move to Cloud: inventory apps and custom code, clean up unused data, run a trial migration, and map timelines against the March 28, 2029 end-of-life date. Start early, since app availability and licensing shift over time.
Questions about your own experience
Expect these behavioral prompts and prepare short stories:
- “Describe a workflow you designed or improved.”
- “Tell me about a time Jira data didn’t match reality. What did you do?”
- “How did you introduce Jira to a team resistant to change?”
- “What’s the worst Jira configuration mess you inherited?”
Structure answers as situation, what you did, and the result, with numbers where possible, such as “cut our average ticket cycle time” or “reduced dashboards from 40 to 8.”
How to answer well
- Answer in context. Say which role you’re answering from (admin, Scrum Master, QA).
- Show a real example for each concept, ideally with a JQL query or an automation rule.
- Mention the trade-off. More custom fields and workflows mean more flexibility but harder reporting.
- Know your edition. State whether you’ve worked in Cloud, Data Center, team-managed, or company-managed projects.
Ways to prove your Jira skills
Nothing beats having something to show. Build a small sample project, then document your workflow design, a few JQL queries, a dashboard, and an automation rule. A simple online portfolio can hold screenshots and short write-ups for recruiters to browse.
Aside: If you want a site for that, HostingFirst’s page (updated September 27, 2026) lists a Hostinger business hosting deal where the Unlimited (Business) plan costs $3.99 per month on a 48-month term, with a renewal price of $16.99 per month. A free portfolio on GitHub Pages or a blog platform works too, so don’t feel you need to pay.
Quick answers
Is Jira only for software teams? No. Teams in marketing, HR, finance, and operations use it for task tracking, and Jira Service Management handles support work.
Do I need to know JQL for an interview? Almost certainly. Be able to write a handful of queries from memory.
What’s the best way to learn Jira quickly? Use a free Cloud site, build a Scrum project, run a mock sprint, write queries, build a dashboard, and create two automation rules.
Are certifications worth it? They can help you stand out for admin roles, but hands-on projects usually carry more weight.
Should I mention AI features? Yes, briefly, and with a note on review and governance.
P.S. If you decide to wait for the sale, HostingFirst’s roundup lists an exclusive Hostinger Black Friday deal with the Unlimited plan at 79% off ($3.99 per month), and says the sale window runs from October 19 to December 14, 2026 (Black Friday is November 27). Promotional prices apply to the first term only, so confirm the renewal rate at checkout.