Jira Administration: Permissions, Notifications, Schemes

What Is a Permission Scheme? - Jira Administration

A Permission Scheme in Jira is a set of rules that defines who can do what within a project.

Think of it as an access-control system. It controls actions such as:

• Creating issues

  Advertisement

• Editing issues

• Deleting issues

• Assigning issues

• Transitioning issues

• Adding comments

• Logging work

• Closing bugs

Analogy

Think of a building:

• The receptionist can open the front door.

• Managers can enter meeting rooms.

• Admins can access every room.

Similarly, in Jira:

• Developers may only edit development-related tasks.

• Testers may only transition bugs.

• Project Managers can close issues.

All of this is controlled through the Permission Scheme.

Why It Matters

Without permission schemes, any user could modify any issue, creating confusion and security risks.

Permission schemes help to:

• Protect sensitive workflows

• Define role-based access

• Prevent unauthorized changes

• Maintain consistency across projects

Key Permissions in a Permission Scheme

How Permission Schemes Work

A Jira administrator:

1. Creates a permission scheme.

2. Assigns permissions (such as Edit Issues) to users, groups, or project roles.

3. Applies the scheme to one or more projects.

The same permission scheme can be reused across multiple projects.

Example: Dev Team Permission Scheme

Interview Answer

"In Jira, we use permission schemes to control what users can do within a project. For example, only the QA team can transition bugs to 'Ready for Retest,' while only the Project Manager can close tickets. Permission schemes provide role-based access, prevent unauthorized changes, and ensure users have only the permissions required for their responsibilities. Our Jira administrator assigns permission schemes to projects, and we reuse the same scheme across similar projects to maintain consistency."

Setting Permissions for Roles (QA, Developer, Manager)

Jira manages permissions through Permission Schemes that are linked to projects and combined with Project Roles such as QA, Developers, and Project Managers.

Users or groups are assigned to these project roles.

Assigning Permissions

Permissions commonly assigned include:

• Browse Projects

• Create Issues

• Edit Issues

• Transition Issues

• Resolve Issues

• Close Issues

• Manage Sprints

• Administer Projects

QA Role

Typical permissions include:

• Browse Projects

• Create Issues (log bugs)

• Edit Issues

• Transition Issues

Developer Role

Typical permissions include:

• Browse Projects

• Edit Issues

• Resolve Issues

• Transition Issues

Manager Role

Managers typically receive higher-level permissions, including:

• Administer Projects

• Manage Sprints

• Manage Users

Permission schemes can be customized according to project requirements, and users can be assigned to roles directly or through group membership.

Interview Answer

"In Jira, permissions are managed through permission schemes linked to projects. Different permissions are assigned to project roles such as QA, Developers, and Managers. QA members can create and update issues, developers can resolve and transition issues, and managers have administrative permissions to manage projects and workflows. This ensures that every user has access appropriate to their responsibilities."

Setting Up Notifications

What Are Notifications?

Notifications are automatic emails or alerts sent when specific events occur, such as:

• Issue Created

• Issue Assigned

• Issue Updated

• Comment Added

• Issue Resolved

• Issue Closed

They help keep team members informed about relevant changes.

How Notifications Work

Notifications are managed through Notification Schemes.

A Notification Scheme defines who receives notifications for different events based on:

• Project Roles

• Groups

• Individual Users

• Assignee

• Reporter

• Watchers

Steps to Set Up Notifications

Go to Jira Administration

• Click the Gear Icon (top-right corner).

Navigate to:

Administration → System (or Projects, depending on your permissions)

Open Notification Schemes

Under the Issues section, click:

Notification Schemes

Create or Edit a Notification Scheme

The scheme contains events such as:

• Issue Created

• Issue Updated

• Issue Resolved

• Issue Assigned

For each event, specify recipients such as:

• Assignee

• Reporter

• Project Role

• Group

Assign the Scheme to a Project

Navigate to:

Project Settings → Notifications

Assign the required Notification Scheme.

Types of Notification Recipients

Notifications can be sent to:

• User who triggered the event

• Assignee

• Reporter

• Project Roles

• Groups (such as jira-users)

• Individual users

• Watchers

Additional Features

Users can:

• Watch issues to receive updates.

• Customize email notification preferences.

• Integrate Jira with Slack or Microsoft Teams for notifications.

Interview Answer

"In Jira, notifications are managed through Notification Schemes that define who receives alerts for events such as issue creation, updates, assignments, and resolutions. Administrators configure these schemes and assign them to projects. For example, when a bug is assigned, both the assignee and reporter automatically receive email notifications. Users can also watch issues to receive updates, ensuring the entire team stays informed and improving collaboration."

Workflow Scheme vs Screen Scheme

Workflow Scheme

A Workflow Scheme maps one or more workflows to specific issue types.

It defines how different issue types move through statuses and transitions during their lifecycle.

For example:

• Bugs can have one workflow.

• Tasks can have another workflow.

• Change Requests can have a different workflow.

Workflow schemes enforce different business processes for different issue types.

Screen Scheme

A Screen Scheme controls which screens are displayed during different issue operations.

These operations include:

• Create

• Edit

• View

It also determines which fields appear on those screens.

For example:

• Some fields may appear only during issue creation.

• Other fields may be visible only while editing.

Screen Schemes are linked to issue types through an Issue Type Screen Scheme.

Difference Between Workflow Scheme and Screen Scheme

Interview Answer

"A Workflow Scheme maps workflows to issue types and controls how issues move through different statuses and transitions during their lifecycle. A Screen Scheme determines which screens and fields users see during Create, Edit, and View operations. Together, they customize both the business process and the user interface for different issue types within a Jira project."

Managing Releases and Versions

Creating Versions

In Jira, Versions represent specific product releases or milestones.

Versions are created under:

Project Settings → Releases (or Versions)

Each version contains:

• Name

• Start Date

• Release Date

• Description

Assigning Issues to Versions

Stories, Bugs, and Tasks are assigned a Fix Version.

This identifies the release in which the issue will be delivered or fixed.

Tracking Versions

Jira tracks release progress based on:

• Completed Issues

• Remaining Issues

Progress can be viewed using:

• Release Hub

• Version Report

• Release Burndown Report

Releasing Versions

Once all issues are completed and verified, the version is marked as Released.

This informs stakeholders that the release is complete.

Planning and Reporting

Versions help teams:

• Plan releases

• Organize sprints

• Prioritize issues

• Track release readiness

Useful reports include:

• Version Report

• Release Burndown

Interview Answer

"I managed releases in Jira by creating Versions for each product release. Issues were assigned a Fix Version to indicate which release they belonged to. I monitored release progress through Jira's Release Hub and Version Reports, and once all issues were completed and verified, I marked the version as Released to keep stakeholders informed."

Customizing Jira for a QA Team

Create Custom Issue Types

In addition to standard issue types such as:

• Bug

• Task

• Story

Create QA-specific issue types like:

• Test Case

• Test Execution

• Test Plan

This clearly separates testing artifacts from development work.

Define Custom Workflows

Example Bug Workflow

New → Open → In Progress → Ready for Retest → Closed

Example Test Case Workflow

Draft → Ready for Review → Approved → Executed

You can configure:

• Transitions

• Conditions

• Validators

to match your QA process.

Add Custom Fields

Create QA-specific fields such as:

• Environment (Staging, Production)

• Severity

• Priority

• Steps to Reproduce

• Test Data

• Root Cause Analysis

Fields can be made:

• Required

• Optional

• Visible only on specific screens

Configure Screens and Field Layouts

Customize the:

• Create Screen

• Edit Screen

• View Screen

Display only the fields relevant to each operation.

Use Components

Create Components based on:

• Modules

• Features

• Application Layers

This helps organize bugs and test cases by ownership.

Configure Issue Security and Permission Schemes

Control who can:

• View Issues

• Create Issues

• Edit Issues

• Transition Issues

For example:

• Restrict deleting bugs.

• Allow only QA Leads to edit test cases.

Configure Filters and Dashboards

Create QA-specific filters such as:

• Open Bugs in Testing

• Failed Test Cases

Useful dashboard gadgets include:

• Filter Results

• Pie Chart

• Two-Dimensional Filter Statistics

• Defect Aging

• Test Execution Progress

Integrate Test Management Plugins

Install plugins such as:

• Zephyr

• Xray

• TestRail

These provide:

• Test Cycles

• Test Execution

• Traceability

• Advanced Reporting

Automate Notifications

Configure:

• Notification Schemes

• Automation Rules

To reduce manual communication and keep the QA team informed.

Interview Answer

"For better QA visibility, I customize Jira by creating issue types such as Test Case and Test Execution, defining QA-specific workflows, adding custom fields, configuring screens, and building QA-focused dashboards. I also integrate test management tools like Zephyr or Xray to manage test cycles and reporting. Finally, I automate notifications to reduce manual effort and improve collaboration across the team."

FAQs

What is a Permission Scheme in Jira?

A Permission Scheme is a set of rules that defines who can perform specific actions within a Jira project, such as creating, editing, assigning, transitioning, or closing issues.

How do you set permissions for QA, Developers, and Managers?

Permissions are assigned to project roles within a Permission Scheme. QA members typically have permission to create, edit, and transition issues; developers have permission to resolve and transition issues; and managers have administrative permissions. The scheme is then linked to the project.

How do you set up notifications in Jira?

Create or edit a Notification Scheme under Administration → Issues, map issue events to recipients such as Assignees, Reporters, Roles, Groups, or Watchers, and assign the scheme to the project.

What is the difference between a Workflow Scheme and a Screen Scheme?

A Workflow Scheme controls issue workflows, including statuses and transitions, while a Screen Scheme controls which screens and fields are displayed during Create, Edit, and View operations.

How do you manage Releases and Versions in Jira?

Create Versions in Project Settings, assign issues using the Fix Version field, monitor progress through the Release Hub or Release Burndown, and mark the Version as Released once all work is complete.

How do you customize Jira for a QA team?

Customize Jira by creating QA-specific issue types, workflows, custom fields, screens, permission schemes, dashboards, and filters. Integrate plugins such as Zephyr or Xray to support test management and reporting.