email settings and mail server logs<\/strong> to find any delivery issues. Following these steps usually identifies why notifications are failing.<\/p>\n\n\n\nQ51. What is a Permission Scheme in JIRA?<\/h3>\n\n\n\n
A permission scheme is a named collection of settings that controls who can perform which actions in a project. It governs actions like creating issues, assigning them, transitioning them, and administering the project. A single permission scheme can be applied to multiple projects, which makes it easier to enforce consistent access rules across a JIRA instance without configuring each project individually.<\/p>\n\n\n\n
Q52. What is a Notification Scheme in JIRA?<\/h3>\n\n\n\n
A notification scheme defines which users or groups receive email alerts when specific issue events occur. Events include issue creation, status changes, comments, assignments, and priority updates. Each event can be mapped to individuals, project roles, reporters, assignees, or watchers. Notification schemes are applied at the project level and can be shared across multiple projects.<\/p>\n\n\n\n
Q53. What is the difference between a Project Role and a Group in JIRA?<\/h3>\n\n\n\n
A Group is a global collection of users managed at the instance level by a site administrator. A Project Role is project-specific and lets you assign different sets of users to different roles within individual projects. Groups are useful for granting global permissions, while Project Roles give you the flexibility to control access on a project-by-project basis without changing global group memberships.<\/p>\n\n\n\n
Q54. What is an Epic in JIRA and how is it different from a Story?<\/h3>\n\n\n\n
An Epic is a large body of work that spans multiple sprints and acts as a container for related Stories, Tasks, and Bugs. A Story represents a single unit of user-facing functionality that is typically small enough to complete within one sprint. Epics provide the high-level view of an initiative while Stories capture the individual, deliverable pieces that make it up.<\/p>\n\n\n\n
Q55. How does Sprint Planning work in JIRA?<\/h3>\n\n\n\n
Sprint planning in JIRA starts in the Backlog view. The team reviews prioritised issues, estimates effort using story points or time, and drags selected issues into the sprint. Once the sprint capacity is filled, the sprint is started with a defined goal and end date. The Scrum board then reflects the active sprint and shows issue progress in real time across status columns.<\/p>\n\n\n\n
Q56. What is Velocity in JIRA and why does it matter?<\/h3>\n\n\n\n
Velocity is tracked in the Velocity Chart and shows how many story points a team completes per sprint over time. It helps teams make more accurate predictions about how much work they can commit to in future sprints based on past performance. A consistent velocity indicates a stable, well-calibrated team, while sudden drops or spikes are signals to investigate what changed in that sprint.<\/p>\n\n\n\n
Q57. How do you use JIRA Automation to reduce manual work?<\/h3>\n\n\n\n
JIRA Automation lets you create rules using a trigger-condition-action model without writing code. For example, you can set a rule to automatically transition an issue to In Review when a linked pull request is opened, or notify a Slack channel when a critical bug is created. Rules can be scoped to a single project or applied across the entire JIRA instance, and they significantly reduce repetitive admin overhead in large projects.<\/p>\n\n\n\n
Q58. What is a Release in JIRA and how do you manage it?<\/h3>\n\n\n\n
A Release, also called a Version, groups issues planned for a specific product update or deployment. You create versions in the project settings, assign issues to them using the Fix Version field, and track readiness using the Version Report and Release Burndown chart. When all issues in a version are resolved, you mark it as Released in JIRA to close out that delivery milestone.<\/p>\n\n\n\n
Q59. How does JIRA integrate with GitHub or Bitbucket?<\/h3>\n\n\n\n
JIRA integrates with GitHub and Bitbucket through Atlassian’s native connectors. Once connected, developers reference a JIRA issue key such as PROJ-101 in their commit messages, branch names, or pull request titles. JIRA then displays the linked commits, branches, and pull request status directly on the issue page, giving project managers full visibility into development activity without leaving JIRA.<\/p>\n\n\n\n
Q60. What is Atlassian Rovo and how does it work inside JIRA?<\/h3>\n\n\n\n
Rovo is Atlassian’s AI solution built natively into JIRA Cloud. It connects data across JIRA, Confluence, and third-party apps to deliver context-aware assistance. Inside JIRA, Rovo agents can be assigned work items directly, mentioned in comments using @Rovo for in-context help, and embedded into workflows so they execute and update tasks alongside human team members. Rovo respects existing project configurations, permission schemes, and audit trails, making it safe to adopt at enterprise scale.<\/p>\n\n\n\n
Bonus Section : Scenario-Based JIRA Interview Questions With Detailed Explanations<\/h2>\n\n\n\n
Understanding how JIRA is used in real work environments is just as important as knowing its features. Many interviews test your ability to solve practical project challenges using JIRA rather than just recalling definitions. The following questions reflect real workplace situations and include detailed explanations to help you understand the reasoning behind each approach.<\/p>\n\n\n\n
1. A developer reports that an assigned task is not visible on their board. What steps would you take to resolve this?<\/strong>
Start by checking the board filter to ensure the issue belongs to the correct project and matches the filter criteria. Next, verify that the issue status is mapped to an active column on the board, since unmapped statuses may hide issues. Also confirm the issue is assigned correctly and included in the active sprint if Scrum is used. Finally, check the user\u2019s project permissions to ensure they have access to view the issue.<\/p>\n\n\n\n2. Your team needs to track bugs separately from feature development within the same project. How would you organize this in JIRA?<\/strong>
Create separate issue types such as Bug and Story or Feature so that each category can be tracked independently. Configure workflows specific to each issue type if the processes differ, such as different approval stages for bugs. Use components, labels, or custom fields to group related items and improve filtering. This setup helps teams prioritize work efficiently and generate meaningful reports.<\/p>\n\n\n\n3. A project manager requests a weekly summary of completed tasks by each team member. How would you implement this?<\/strong>
Create a filter that displays issues completed within the past week and group them by assignee. Add gadgets such as Created vs Resolved Chart or Workload Pie Chart to a dashboard for visual tracking. Configure the dashboard to automatically send scheduled email reports to stakeholders. This reduces manual reporting effort and ensures consistent visibility into team performance.<\/p>\n\n\n\n4. A sprint is already running, and an urgent task must be included immediately. How would you manage this change?<\/strong>
Add the urgent issue directly into the active sprint through the backlog view. Inform the Scrum Master and team members so they can evaluate how the new task affects sprint commitments. If the sprint workload becomes too heavy, consider removing or postponing lower-priority tasks. This keeps the sprint manageable while still addressing critical requirements.<\/p>\n\n\n\n5. Your team frequently assigns bugs to the same developer and wants to reduce manual effort. What approach would you use?<\/strong>
Use JIRA Automation to create a rule triggered when a new issue is created. Add a condition to check whether the issue type is Bug or matches specific criteria. Configure an action that automatically assigns the issue to the designated developer or team member. This saves time, ensures consistency, and reduces the chance of assignment delays.<\/p>\n\n\n\n6. A manager wants to track tasks that are blocked due to dependencies. How would you handle this requirement?<\/strong>
Use issue linking options such as \u201cblocks\u201d or \u201cis blocked by\u201d to define relationships between tasks. Create filters that display blocked issues and highlight them on dashboards for visibility. Encourage team members to update links whenever dependencies change. This makes it easier to identify bottlenecks and resolve delays quickly.<\/p>\n\n\n\n7. Closed issues should not be edited by general users. What configuration changes would you make?<\/strong>
Update the workflow to restrict editing once an issue reaches the Closed status. Add conditions or validators that prevent users from modifying fields after closure. Adjust permission schemes so only administrators or authorized roles can edit closed issues if necessary. This protects completed records and maintains data integrity.<\/p>\n\n\n\n8. Several tasks were mistakenly moved to the wrong sprint. How would you correct this efficiently?<\/strong>
Open the backlog and locate the misplaced tasks, then move them to the correct sprint manually. If many tasks are affected, use the bulk change feature to update the sprint field for multiple issues at once. After moving them, review sprint details to confirm accuracy. This ensures the sprint backlog reflects the correct workload.<\/p>\n\n\n\n9. The organization wants to track time spent on tasks for billing and productivity analysis. How would you set this up?<\/strong>
Enable time tracking in project settings so users can log hours directly within issues. Add original estimates to tasks to compare planned time against actual time spent. Encourage team members to regularly log their work using the worklog feature. Use time tracking reports to generate insights useful for billing and performance reviews.<\/p>\n\n\n\n10. Team members complain about receiving too many notifications from JIRA. How would you reduce notification overload?<\/strong>
Review the notification scheme and identify events that trigger unnecessary emails. Remove or modify notifications that are not critical, such as minor updates or field changes. Encourage users to customize their personal notification settings to receive only relevant updates. This helps reduce distractions and improves overall productivity.<\/p>\n\n\n\nAdditional Read<\/strong>:<\/em> Answers To 10 Most Common Job Interview Questions<\/strong><\/a><\/p>\n\n\n\nIf you are curious about project management, issue tracking, and team collaboration, then join HCL GUVI<\/strong>‘s comprehensive and insightful JIRA Project Management Course<\/a><\/strong> and delve deep into agile methodologies, customizable workflows, and real-time insights.<\/p>\n\n\n\nLooking to move beyond basic ChatGPT skills? Here\u2019s your chance to be a part of Be part of the Bharat AI Initiative, a nationwide movement by HCL GUVI, in association with OpenAI, built to help India\u2019s youth develop advanced ChatGPT skills absolutely free! Learn structured prompting, refine responses with clarity, and apply ChatGPT more effectively in projects, assignments, and everyday work. Learn in English, Hindi, Marathi, Tamil, or Telugu and start your free AI journey!<\/strong><\/p>\n\n\n\nJoin the Movement<\/a><\/strong><\/p>\n\n\n\n\n
\ud83d\udca1 Did You Know?<\/h3>\n \n - JIRA was first released in 2002 as a simple bug tracker and has since evolved into a full AI-powered work management platform used by over 300,000 organisations worldwide.<\/li>\n
- The name JIRA comes from “Gojira,” the Japanese word for Godzilla, created as a playful reference to its original competitor, Bugzilla.<\/li>\n
- Atlassian officially ended support for the JIRA Server version in February 2024, moving teams toward JIRA Cloud or JIRA Data Center solutions.<\/li>\n <\/ul>\n<\/div>\n\n\n\n
![\"Top](\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/01\/01@2x-1-1-1200x630.png\" "\\"\\"")
<\/figure>\n\n\n\n