Jira Interview Questions & Answers (2026)
These interviews test your practical knowledge of Jira administration, workflow customization, and agile reporting. Show you can configure schemes, resolve permission conflicts, and extract metrics that drive sprint decisions. Demonstrate clear reasoning, best‑practice trade‑offs, and how you’d scale solutions across teams to succeed.
23 questions · updated Aug 29, 2026
Quick facts
| Typical rounds | Phone screen → Technical deep‑dive → Hands‑on task → Manager interview |
| Core topics | Projects, issue types, workflows, permissions, agile boards, reporting |
| Preferred experience | 2–4 years of Jira admin or heavy user experience |
| Common tools | Jira Cloud, Jira Server, ScriptRunner, REST API |
| Key metrics | Cycle time, sprint velocity, issue aging, resolution rate |
Questions
Beginner
What is the difference between a Jira project and a Jira board?
A project is a container for issues, schemes, and configurations; it defines the data model, permissions, and global settings. A board is a view layer that pulls issues from one or more projects based on a filter and displays them in a kanban or scrum format. Interviewers expect you to explain that boards do not store data, so changes to a board affect only the UI, while project changes affect the underlying issue lifecycle and permissions.
How do you restrict a user from editing a specific issue type while allowing them to view it?
Create a custom Permission Scheme, then add a ‘Edit Issues’ permission entry with a JQL condition that excludes the target issue type. Alternatively, use a Workflow Property (jira.permission.editable = false) on the transition that leads to the restricted issue type. The interviewer wants to see that you understand both permission schemes and workflow‑level controls, and that you can combine them to meet fine‑grained security requirements.
Explain how Jira’s issue security levels work and when you would use them.
Issue security levels are part of a Security Scheme that assigns a set of groups, project roles, or single users to each level. When an issue is set to a level, only members of that level can view the issue. Use cases include confidential HR tickets, legal matters, or customer‑specific bugs that only a subset of the team should see. Interviewers look for clarity on the hierarchy, the need for a default level, and the impact on reporting and notifications.
What is a workflow scheme and why would you use multiple schemes in one Jira instance?
A workflow scheme maps issue types to specific workflows. Using multiple schemes lets you tailor the lifecycle for different project domains—e.g., a bug workflow with QA steps versus a feature workflow with design and review stages. This separation reduces complexity, enables independent evolution, and respects governance policies across teams. Interviewers expect you to discuss the trade‑off between maintainability and the overhead of managing many schemes.
How can you bulk change issue types without losing custom field data?
Use the Bulk Change tool, select ‘Move Issues’, and choose the target issue type. Ensure the custom fields are present in both source and destination issue type screens; otherwise, Jira will drop values. A strong candidate mentions testing on a sandbox, verifying field configurations, and using the ‘Retain values’ option where applicable, showing awareness of data integrity risks.
Intermediate
Describe how you would implement a ‘Definition of Done’ checklist that appears on every issue transition.
Add a Workflow Property (jira.issue.editable = false) on the transition and attach a ‘Done’ screen containing a checklist custom field (e.g., a multi‑select or checkbox). Use a Validator (e.g., ‘Field Required’) to enforce completion before the transition can proceed. Interviewers want to see that you can combine properties, screens, and validators to embed process rigor while keeping the UI intuitive.
How do you migrate a Jira Server project to Jira Cloud while preserving custom workflows?
Export the project using Project Export (XML) and import it into Cloud via the Migration Assistant. Prior to migration, ensure all apps used in the workflow (e.g., ScriptRunner) are available in Cloud, or replace them with native Cloud equivalents. Validate post‑migration by comparing workflow steps, conditions, and post‑functions. The interviewer looks for awareness of compatibility gaps, testing strategy, and rollback planning.
What is the purpose of a ‘Screen Scheme’ and how does it differ from a ‘Field Configuration Scheme’?
A Screen Scheme maps issue operations (Create, Edit, View) to specific screens, controlling which fields appear at each step. A Field Configuration Scheme maps issue types to field configurations, dictating field behavior (required, hidden, optional). Together they define UI and data rules. Interviewers expect you to articulate the separation of presentation (screens) from field behavior (field config) and why that modularity matters for large instances.
Explain how Jira’s REST API can be used to automate sprint creation and what permissions are required.
POST to /rest/agile/1.0/sprint with JSON payload containing name, startDate, endDate, and boardId. The caller must have ‘Manage Sprints’ permission on the board’s project. A good answer mentions handling rate limits, using OAuth or API tokens, and verifying the sprint appears in the board’s backlog. Interviewers look for practical API usage, security awareness, and error‑handling considerations.
How would you troubleshoot a scenario where a custom field is not appearing on a screen despite being added to the field configuration?
First, verify the field is on the screen associated with the operation via the Screen Scheme. Next, check the Field Configuration Scheme to ensure the field is not hidden or optional. Confirm the issue type uses the correct scheme. Finally, clear browser cache or test in incognito mode to rule out UI caching. Interviewers want a systematic approach that covers scheme mapping, UI caching, and permission checks.
What are the trade‑offs between using native Jira automation rules versus a third‑party add‑on like ScriptRunner?
Native automation offers a low‑code, cloud‑compatible solution with built‑in audit logs and limited runtime, ideal for most use cases. ScriptRunner provides deeper scripting (Groovy), access to internal APIs, and complex conditional logic, but adds maintenance overhead, licensing cost, and potential upgrade friction. Interviewers expect you to weigh flexibility against stability, cost, and team skill set when recommending a solution.
How can you configure a Jira board to show only issues that are tagged with a specific component?
Create a board filter using JQL: project = XYZ AND component = "Frontend". Assign this filter to the board’s configuration. Ensure the board’s swimlanes or quick filters do not override the base filter. The interviewer looks for knowledge of JQL, board filter assignment, and the impact on backlog grooming and reporting.
Advanced
Describe how you would set up a ‘Release Hub’ view that aggregates issues across multiple projects for a single release.
Create a Release Version in each project that shares a common naming convention (e.g., 2026.Q3). Then build a JQL filter: fixVersion in ("2026.Q3") AND project in (PROJ1, PROJ2, PROJ3). Use the Release Hub gadget or a custom Dashboard with the filter to display aggregated issues, burndown, and release notes. Emphasize coordination of version naming, filter maintenance, and stakeholder communication.
How do you implement a global permission that prevents any user from deleting issues after a certain date?
Create a Permission Scheme with the ‘Delete Issues’ permission granted only to a dedicated admin role. Then add a Workflow Property (jira.permission.delete = false) on the transition that leads to the final status, combined with a Condition that checks the issue’s created date via a ScriptRunner validator. This layered approach shows you can enforce policy both at permission and workflow levels, satisfying compliance needs.
What is the impact of enabling ‘Issue Indexing’ on performance, and how would you mitigate any slowdown?
Issue indexing updates the Lucene index on every change, which can increase CPU and I/O load, especially in large instances with frequent updates. Mitigation strategies include increasing JVM heap, tuning the indexing thread pool, scheduling bulk re‑index during off‑peak hours, and disabling unnecessary custom fields that trigger re‑index. Interviewers expect you to discuss both resource implications and practical tuning steps.
Explain how you would design a workflow that enforces code review before a bug can be marked ‘Done’.
Add a transition ‘Ready for Review’ with a Condition that checks a custom field ‘Code Review Approved’ = Yes. Use a Validator that calls the Bitbucket API (via ScriptRunner) to verify at least one pull request is merged. Only after this transition can the issue move to ‘Done’. This demonstrates linking Jira to source control, using conditions/validators, and preserving traceability.
How would you use Jira’s ‘Data Center’ clustering features to achieve high availability?
Deploy Jira Data Center nodes behind a load balancer, configure shared file system for attachments and indexes, and enable sticky sessions for session replication. Use a database cluster (e.g., PostgreSQL streaming replication) for persistence. The answer should cover node scaling, failover testing, and monitoring of cluster health, showing you understand both architecture and operational considerations.
What are the considerations when migrating custom JQL functions from ScriptRunner to native Jira Cloud?
Native Cloud lacks Groovy, so custom functions must be rewritten using Jira Expressions or Automation rules. Evaluate performance impact, expression limits, and security sandboxing. Provide a migration plan: catalog functions, map to equivalents, test on a sandbox, and update saved filters. Interviewers look for awareness of functional gaps, rewrite strategies, and validation steps.
How can you generate a sprint report that excludes issues from a specific epic?
Create a custom JQL filter for the sprint: sprint = 42 AND "Epic Link" != EPIC-123. Use the ‘Sprint Report’ gadget with this filter, or export the sprint data via the REST API and apply the exclusion in post‑processing. The interviewer expects you to discuss filter composition, gadget configuration, and potential pitfalls like epics without linked issues.
Describe the process for auditing permission changes across multiple Jira projects.
Enable the ‘Audit Log’ at the global level, then use the REST endpoint /rest/api/3/audit/record to retrieve entries filtered by ‘Permission Scheme’ and date range. Export results to CSV for analysis. For deeper insight, integrate with Splunk or an SIEM via webhook. Interviewers want a systematic approach that combines built‑in logging, API extraction, and external analysis for compliance.
How would you design a permission model that allows contractors to view but not edit any issues in a client project?
Create a Project Role ‘Contractor’ and assign it to the external users. In the Permission Scheme, grant ‘Browse Projects’ to the role, but omit ‘Edit Issues’. For any issue types that must be hidden, add an Issue Security Scheme with a level that excludes the contractor role. This layered model shows you can combine role‑based permissions with issue‑level security to meet contractual constraints.
What is the effect of enabling ‘Issue Linking’ across projects, and how do you control link visibility?
Cross‑project linking allows issues to reference each other, facilitating traceability. Visibility is governed by the ‘Link Issues’ permission and the target issue’s security level. To control exposure, restrict the permission to specific roles and ensure linked issues share compatible security schemes. Interviewers expect you to discuss both functional benefits and the security implications of linking sensitive data across project boundaries.
How can you automate the transition of issues that have been in ‘In Progress’ for more than 10 days to ‘Stale’?
Create an Automation rule: Trigger – Scheduled (daily). Condition – JQL: status = "In Progress" AND updated <= -10d. Action – Transition issue to ‘Stale’. Add a comment explaining the move. This demonstrates knowledge of scheduled triggers, JQL date functions, and safe automated state changes.
Common mistakes
- Confusing Permission Schemes with Workflow Schemes, leading to unexpected access.
- Modifying screens without updating the associated Screen Scheme, causing fields to disappear.
- Relying on a single JQL filter for multiple boards, which can create performance bottlenecks.
- Over‑customizing workflows without documenting post‑functions, making maintenance hard.
- Neglecting to test migrations in a sandbox, resulting in lost data or broken integrations.
Study plan
- Review core Jira concepts: projects, issue types, schemes, and boards.
- Practice configuring permissions, workflows, and screens in a test instance.
- Solve at least 10 real‑world JQL scenarios and automate them with native rules.
- Run a mock migration or API script to solidify hands‑on experience.
- Create a cheat sheet of common pitfalls and their resolutions.
FAQ
Do I need to know Jira scripting languages for most interviews?
Not always. Many companies focus on native configuration and automation. Knowing basic Groovy or ScriptRunner helps for advanced roles, but you can succeed by mastering screens, workflows, and REST API usage.
How important is Agile knowledge when answering Jira questions?
Very important. Jira is often used to support Scrum or Kanban processes, so expect questions about sprint metrics, board filters, and how configuration supports agile ceremonies.
Can I use the same answer for both Jira Cloud and Server?
Generally yes, but note differences in app availability, API endpoints, and licensing. Highlight any Cloud‑only limitations or Server‑only features when relevant.
What should I demonstrate when asked about performance tuning?
Mention indexing, JVM heap sizing, database connection pooling, and limiting custom fields. Show you can identify bottlenecks and apply concrete configuration changes.
Is it enough to memorize JQL syntax?
Memorization helps, but interviewers value your ability to construct queries for business needs, combine filters, and explain trade‑offs. Practice building queries from real scenarios.
Related
Ready for your next interview?
Download MiPrep AI. Load your resume and the job description. Show up ready.
Free tier · No credit card · macOS 14+ · Windows 10+
Free tier · No credit card · Runs on your Mac or Windows machine