Key Highlights, Jira Interview Questions and Answers Jira AI features (Atlassian Intelligence) are now expected knowledge for any role involving Jira administration or team tooling. Jira Service Management questions now appear regularly in non-IT roles because HR, legal, and facilities teams have adopted JSM. Jira Automation is one of the most underused features and one of the most asked-about in interviews. Know it. The “how would you set up a Scrum project from scratch” question appears in over 70% of Scrum Master and agile coach interviews that mention Jira. JQL (Jira Query Language) proficiency is a filter that most interviewers use to distinguish experienced Jira users from casual ones. Understanding how to create a Scrum project in Jira and Jira alternatives for agile teams is directly relevant to interview prep. What Jira Interviews Test in 2026 Jira questions show up across a wide range of roles, Scrum Masters, agile coaches, project managers, product owners, and dedicated Jira admins all face them. The format varies by seniority. Entry-level interviews lean on conceptual questions like “what is the difference between a bug and a sub-task?” Mid-level interviews move to configuration, “how would you set up a Kanban board for an ops team?” Senior and admin interviews shift to governance and scenario questions, “you have 500 custom fields and performance is degrading , what do you do?” Know the why behind each concept, not just the name of the thing.
8 Jira Fundamentals Interview Questions Q1. What is Jira and what is it used for? Jira is Atlassian’s project and issue tracking platform. Jira Software is used by development and delivery teams to plan, track, and ship work, it supports Scrum boards, Kanban boards, and backlog management. Jira Service Management is used by IT, HR, legal, and operations teams to manage service requests, incidents, and changes. Jira Work Management is for business teams running projects without software delivery. In 2026, most enterprise users encounter Jira Software and Jira Service Management.
Q2. What are the main issue types in Jira Software? The default issue hierarchy in Jira Software, Epic (large body of work spanning multiple sprints), Story (a unit of user-facing functionality, typically completable in one sprint), Task (non-story work like documentation or setup), Sub-task (a breakdown of a story or task into smaller steps), and Bug (a defect requiring a fix). In next-gen (team-managed) projects, the hierarchy is Epics, Stories/Tasks, and Sub-tasks. In classic projects, you can customise the issue type scheme for the project.
Q3. What is the difference between a Scrum board and a Kanban board in Jira? A Scrum board is sprint-based, issues are pulled into a sprint from the backlog, the board shows only sprint issues, and work is reviewed at sprint end. Sprints have a fixed timeframe. A Kanban board has no sprints, all issues on the board move through columns continuously, and WIP (work in progress) limits are the key control mechanism. Use Scrum when work is organised in time-boxed iterations. Use Kanban when work arrives continuously and predictable cadence is more important than iteration. Kanban vs Scrum covers the strategic differences.
Q4. What is the difference between a classic project and a team-managed project in Jira? Classic (company-managed) projects share their configuration across the Jira instance. The workflow scheme, issue type scheme, and field configuration are all set at the instance level, meaning a change to one affects every project that shares that scheme. Team-managed projects isolate configuration to the project itself, which is why individual teams can self-configure without going through a Jira admin. The trade-off, team-managed projects have fewer customisation options and are harder to standardise across a large delivery organisation. Enterprise teams building consistent processes across multiple squads almost always go with classic, small autonomous teams generally prefer team-managed.
Q5. What is a Jira workflow and what does it consist of? A Jira workflow is the lifecycle map for an issue, the statuses it moves through (To Do, In Progress, Code Review, Done), the transitions between those statuses, and the rules around each transition. Conditions control who is allowed to trigger a given transition. Validators check whether required fields are filled before the move is permitted. Post-functions fire automatically once the transition completes, doing things like auto-assigning the issue to a reviewer or posting a comment. Most teams do not need all three, but understanding the distinction matters in admin interviews.
Q6. What is JQL and when is it used? JQL (Jira Query Language) is Jira’s structured search syntax for finding, filtering, and reporting on issues. Common JQL operators, project = “MYPROJECT” AND status = “In Progress” AND assignee = currentUser() . JQL is used to create custom filters, build Jira dashboards, configure board swimlanes, and create automation rule conditions. JQL proficiency is expected for Scrum Masters, Jira admins, and anyone regularly reporting on project status. Common interview test, “Write a JQL query to find all unresolved P1 bugs assigned to you in the last 30 days.”
Q7. What is the difference between an issue filter and a Jira board? A filter is a saved JQL query that returns a list of issues. A board is a visual representation of a workflow that uses a filter to define which issues appear on it. Every Jira board is backed by a board filter. Understanding this distinction explains why changing a board’s filter changes which issues appear on it, and why you can share a filter with another team to create a board showing the same issues in a different view.
Q8. What are issue links and when do you use them? Issue links create named relationships between Jira issues, “blocks”, “is blocked by”, “relates to”, “duplicates”, “is duplicated by”, “clones”. Use them when a bug is blocking a release story, when two stories in different projects are related, or when an epic has a dependency on another team’s work. Issue links are not a substitute for a proper issue hierarchy, they are for cross-issue relationships that the hierarchy does not capture.
7 Jira Boards, Backlogs, and Sprint Management Interview Questions Q9. How do you set up a Scrum project in Jira from scratch? Create a Scrum project (classic or team-managed depending on admin policy). Configure the issue type scheme if needed. Create epics to represent the main feature areas. Add stories to the backlog under each epic. Estimate stories using story points or time. Configure the board columns to match the team’s workflow (To Do, In Progress, Code Review, Testing, Done). Run sprint planning, select issues from the backlog, set a sprint goal, and start the sprint. The board then shows only the sprint issues. How to create a Scrum project in Jira covers this step by step.
Q10. What is sprint velocity and how is it tracked in Jira? Velocity is the count of story points a team completes in a sprint, and it is the primary input for sprint capacity planning. Jira tracks this in the Velocity Chart report, which shows planned versus completed points across past sprints. The practical rule, average the last three to five sprints, not just the most recent one. A single sprint’s velocity is too sensitive to who was on leave, which stories underran, and whether an incident hit mid-sprint. How to improve team velocity in agile explains what actually drives the number.
Q11. What is the difference between Story Points and Time Estimation in Jira? Story points measure relative complexity, not duration. A story estimated at 5 points takes roughly twice the effort of a 2-point story, but neither of those numbers tells you how many hours it will take. Teams use story points because absolute hour estimates consistently underestimate uncertainty and create false precision. Time estimation in hours is still available in Jira and works fine for sub-tasks or operational work with well-understood scope. Some teams run a hybrid, story points for stories, time estimates for sub-tasks. That works as long as the team is consistent about what each field means.
Q12. How do boards handle issues in multiple statuses on a Jira Kanban board? Each column on a Kanban board maps to one or more workflow statuses. When you configure a Kanban board, you assign each of your workflow statuses to a column. A single column can represent multiple statuses (for example, “In Progress” could map to both “Development” and “Code Review” statuses). WIP limits are set per column in the board settings. When the WIP limit is exceeded, Jira highlights the column to signal the team should pull from it before adding more.
Q13. What is the backlog refinement process in Jira and how does Jira support it? Backlog refinement (grooming) is the ongoing process of reviewing, estimating, and prioritising issues before they enter a sprint. Jira supports this through the backlog view where issues can be reordered by drag-and-drop, epics can be used to filter the backlog, and issues can be estimated and labelled. Jira does not enforce refinement as a process, that is a team practice decision. The Jira Backlog view with epic filtering and bulk editing is the main tool. AI product backlog management covers how AI is augmenting this process in 2026.
Q14. What is a Jira Release (Fix Version) and how is it used? A Fix Version in Jira marks which release an issue is scheduled for or was resolved in. You can filter the backlog by Fix Version to see what is planned for a specific release, track release progress on the Releases screen, and generate a release report showing what completed, what was incomplete, and what was added mid-sprint. Fix Versions are useful for teams working toward a versioned product release, and less relevant for teams practising continuous delivery where every sprint deploys independently.
Q15. How do you handle issues that are not completed at sprint end? When you complete a sprint, Jira asks what to do with incomplete issues, move to the next sprint, move back to the backlog, or move to a different sprint. Most teams move incomplete issues to the next sprint if the work is still valuable and in progress, or back to the backlog for re-prioritisation if priorities shifted. Never auto-close incomplete issues just to keep the sprint “green”, it hides real capacity data and distorts velocity. Sprint retrospectives should include a root cause review of why issues were not completed.
7 Jira Administration and Configuration Interview Questions Q16. What are the main administrator settings in Jira and who controls them? Jira instance administrators control global settings (user management, authentication, mail settings), schemes (issue type schemes, workflow schemes, field configuration schemes, permission schemes, notification schemes), and system settings. Project administrators control project-level settings within their assigned project, including board configurations and project permissions, but cannot modify shared schemes affecting other projects. This separation matters in regulated environments where changes must be controlled and auditable.
Q17. What is a permission scheme in Jira and why does it matter? A permission scheme controls who can perform which actions within a project, who can view issues, create issues, edit issues, transition workflow steps, delete issues, and administer the project. Permission schemes can be shared across multiple projects. In enterprise Jira deployments, poorly configured permission schemes are the most common source of security and audit issues. Always follow the principle of least privilege, grant only the permissions actually needed for each role.
Q18. What are custom fields in Jira and when should you add them? Custom fields add data attributes beyond Jira’s default fields to capture team-specific information, team name, priority tier, customer name, business value score. Adding custom fields has costs, they clutter the issue form for all users, slow down Jira performance at scale, and create reporting complexity. Before adding a custom field, verify that no existing field captures the same information and that the data will actually be used in reporting or automation. Unused custom fields should be archived regularly by a Jira admin.
Q19. What is Jira Automation and what can it do? Jira Automation allows you to set up rules that trigger actions automatically based on events. Example, when an issue moves to “Code Review”, automatically assign it to the reviewer group and send a Slack notification. Another example, when all sub-tasks of a story are closed, automatically close the parent story. Jira Automation replaced third-party plugins for many common workflows and is now included in all Jira plans. Key automation components, Trigger (what starts the rule), Conditions (when the rule applies), and Actions (what happens).
Q20. How do you migrate a team from a legacy tool to Jira? Assessment, document the team’s current workflow, issue types, and terminology. Mapping, map existing issue types and statuses to Jira equivalents. Import, use Jira’s CSV import, the Jira migration assistant, or a dedicated migration tool depending on the source system. Training, run a Jira orientation session before go-live. Parallel run, for high-risk migrations, run both systems for 1 to 2 sprints. Common mistakes, mapping everything 1,1 from the old tool rather than using the migration as an opportunity to simplify, and migrating historical data that will never be referenced again.
Q21. What are Jira components and how are they different from labels? Components are structured sub-categories within a project (UI, API, Authentication) with a default assignee. They are admin-configured and searchable via JQL. Labels are free-text tags that anyone can add, unstructured, and also searchable via JQL. Use components when you want structured categorisation with consistent naming and default routing. Use labels for ad-hoc tagging that does not need consistent governance. Mixing both creates a dual taxonomy problem where teams use them inconsistently, pick one approach and document the convention.
Q22. What is Atlassian Intelligence and what does it add to Jira in 2026? Atlassian Intelligence is the AI layer in Jira (and Confluence) powered by Atlassian’s models and third-party integrations. In Jira Software, it provides, issue summarisation, JQL generation from natural language (“find all high-priority bugs created last week”), automated sprint planning suggestions, and backlog health insights. In Jira Service Management, it powers the virtual service agent. Most teams in 2026 use AI features for JQL assistance and ticket summarisation, adoption of planning suggestions is still early. AI for Jira and Confluence Workshop covers hands-on use of these features.
5 Jira Service Management Interview Questions Q23. What is Jira Service Management and how is it different from Jira Software? Jira Service Management is built for service teams handling requests, incidents, problems, and changes. It has a customer-facing portal where non-Jira users can submit requests, SLA (Service Level Agreement) tracking, change advisory board (CAB) workflows, asset management (CMDB), and a virtual service agent. Jira Software is built for development teams running sprints and managing product backlogs. The two can be linked, JSM incidents can be linked to Jira Software bugs for engineering to fix.
Q24. What is an SLA in Jira Service Management and how is it configured? An SLA defines time limits for responding to and resolving requests based on priority. For example, P1 incidents must have a first response within 1 hour and a resolution within 4 hours. In JSM, SLAs are configured with the time metric (time to first response, time to resolution), the conditions that start and stop the SLA timer, and the working hours calendar. Breached SLAs appear in reports and can trigger automation alerts to escalate to supervisors. Monitoring SLA performance is one of the primary value metrics for service teams.
Q25. What is the change management workflow in Jira Service Management? Change management in JSM handles planned changes to systems or infrastructure with a structured approval process. The standard workflow, Submit change request, Risk assessment, CAB (Change Advisory Board) review, Approved or Rejected, Implementation, Post-implementation review. In JSM, change requests can be integrated with CI/CD pipelines so deployment events automatically create and advance change records. This is a common interview topic for DevOps and ITSM roles working at the intersection of development and operations.
Q26. What is a Jira Service Management virtual service agent? The virtual service agent is a conversational AI bot in JSM that resolves Tier-1 service requests without routing to a human agent. It uses the knowledge base (Confluence or Jira’s native knowledge base) to answer questions and can complete structured tasks like resetting access or routing requests to the correct team. For organisations with high ticket volumes of repetitive requests (password resets, equipment requests, policy questions), the virtual service agent can deflect 30 to 50% of tickets from human queues.
Q27. What is asset management in Jira Service Management? The asset management module (previously called Assets, formerly Insight) is a configuration management database (CMDB) built into JSM Premium. It tracks hardware, software licences, cloud resources, and their relationships. When a P1 incident is raised, the CMDB helps identify which assets are affected and which dependent services are at risk. Asset data can be used in JSM workflows for automatic impact analysis and to pre-populate incident fields. It is particularly valuable for organisations managing large IT estates or complying with ITIL frameworks.
3 Advanced Jira Scenario-Based Interview Questions Q28. A team wants to track bugs for three different product areas on a single Jira board. How would you structure this? Options, use components to tag bugs by product area (UI, API, Backend) and configure swimlanes by component on the board, use separate boards with separate JQL filters per product area sharing the same project backlog, or create separate Jira projects per product area with cross-project dependency links. The right answer depends on team size and reporting needs. For one team working across all three areas, a single project with component-based swimlanes is simplest. For three separate teams, separate projects with a portfolio board at the programme level is more appropriate.
Q29. You notice your Jira instance has 500+ custom fields and performance is degrading. How do you address this? Audit, generate a custom field usage report (Jira admin, then Issues, then Custom Fields, then Usage). Archive or delete fields with zero or near-zero usage. Review fields used in fewer than 5 projects and evaluate whether consolidation is possible. Set up a custom field governance policy, new custom field requests require admin approval and documented business justification. Re-index Jira after removing fields. Going forward, use context-scoped fields (field only appears in specific projects) rather than global fields to limit performance impact.
Q30. How would you use Jira to support a PI Planning event for a scaled agile team? For PI (Program Increment) Planning in Jira for a SAFe organisation, create Epics at the Feature level for each PI feature, create Stories under each Feature assigned to the relevant team and sprint within the PI. Use Fix Versions to represent the PI quarter. Use Jira’s dependency links (blocks/is blocked by) to capture inter-team dependencies identified during planning. Use an Advanced Roadmap (Jira Plans) to visualise cross-team work on a timeline. Post-PI, track commitment at the story level and review against PI objectives at sprint review. What is PI planning in agile and SAFe PI Planning Workshop cover the underlying process.
Conclusion Jira proficiency sits at an interesting place in the skills hierarchy, it is expected for almost every agile delivery role, but it is also something most candidates underestimate until they are in the interview room and asked to write a JQL query from scratch or explain the difference between a company-managed and team-managed project configuration.
The 30 questions above cover the range from someone who uses Jira to track sprint tasks to someone who administers a multi-team instance and configures custom workflows, permission schemes, and Jira Service Management processes. Work through the sections relevant to the role you are applying for, and practise the hands-on configuration exercises before your interview, not during it.
For practitioners who want to go beyond surface-level Jira knowledge and learn how to use it effectively inside an agile delivery system, NextAgile’s Jira Training Masterclass Workshop covers both the tooling and the underlying agile process together. If your team is exploring how AI features in Jira and Confluence can improve delivery speed, the AI for Jira and Confluence Workshop covers the 2026-specific features that most teams have not yet adopted.
Frequently Asked Questions 1.What is the difference between Jira Software and Jira Work Management? Jira Software is designed for software delivery teams running agile sprints and backlogs. Jira Work Management is for business teams running projects like marketing campaigns, HR onboarding, or finance processes, it has forms, calendar views, and timeline views but no Scrum boards or story points.
2.Do I need Jira admin experience to pass a Scrum Master Jira interview? No. Scrum Master interviews expect board configuration, sprint management, backlog management, and JQL, not scheme administration. Admin questions appear in Jira Administrator roles specifically.
3.What is Jira Align and how is it different from Jira Software? Jira Align is Atlassian’s enterprise agile planning tool for scaling agile across portfolios, programmes, and teams. It operates at the Strategy/Solution/Programme/Team hierarchy. Jira Software handles team-level work. Jira Align connects team-level work to programme-level OKRs and PI objectives. It is typically used by organisations with 100+ teams running SAFe or LeSS.
4.What JQL queries should I know for a Scrum Master role? At minimum, unresolved issues in current sprint, issues due this week, bugs opened last 7 days, unestimated stories in the backlog, and issues assigned to a specific person in a specific status. Practise writing these without referencing documentation.
5.How should I prepare for a Jira admin interview? Set up a free Jira Cloud trial. Create a classic project. Configure a custom workflow, add a custom field, write automation rules, and create a permission scheme. The hands-on configuration experience is more valuable than reading documentation.
6.Is Jira experience still relevant given the rise of alternatives like Linear and Monday.com? Jira remains dominant in enterprise and regulated industries. Alternatives like Linear have higher developer satisfaction scores but significantly lower enterprise adoption. For roles at large technology companies, banks, healthcare organisations, or consulting firms, Jira experience is still the expected baseline. Jira alternatives for agile teams covers when alternatives make sense.
Sujith G. is an agile practitioner with expertise in setting up the agile environment by coaching and training teams, individuals and stakeholders in the area of lean agile software principles. He has overall 12+ years of exp out of which 9+ years have been in Agile and Scrum implementation and adoption. Sujith has coached 70+ teams on agile practices & implementation techniques and has extensive experience in setting up metrics, JIRA & Azure DevOps. Experienced in identifying gaps in the system, creating scrum awareness, piloting and scaling scrum.
Skip to content 
