JIRA Integrations and Administration

A JIRA project does not exist in isolation. Development teams use code repositories, communication tools, CI/CD pipelines, and documentation platforms alongside JIRA every day. Connecting these tools to JIRA eliminates the need to switch between applications constantly and keeps all project data visible in one place. On the administration side, JIRA gives administrators full control over users, project configurations, schemes, and system settings.

This topic covers the most important integrations JIRA supports and the key responsibilities of a JIRA administrator.

Part 1 — JIRA Integrations

JIRA integrates with external tools in two main ways: through official Atlassian-built connectors and through the Atlassian Marketplace, which hosts thousands of third-party apps built by other vendors.

What Is a JIRA Integration?

A JIRA integration is a connection between JIRA and another tool that allows data to flow between them automatically. For example, when a developer pushes code to GitHub and references a JIRA issue number in the commit message, JIRA automatically links that commit to the issue and displays it inside the issue detail view.

Developer writes commit message:
"Fix login timeout bug — PROJ-204"

GitHub detects PROJ-204 reference → sends data to JIRA

JIRA PROJ-204 issue now shows:
┌─────────────────────────────────────────────────────┐
│ PROJ-204 — Fix login timeout bug                    │
├─────────────────────────────────────────────────────┤
│ Development                                         │
│  ✔ 1 commit   |  0 branches  |  0 pull requests    │
│  Commit: a3f9c2b — "Fix login timeout bug"          │
└─────────────────────────────────────────────────────┘

GitHub and Bitbucket Integration

Connecting JIRA with GitHub or Bitbucket links development activity directly to JIRA issues. This gives the entire team visibility into the code changes associated with each task.

What Gets Linked Automatically

How to Connect GitHub to JIRA

1. Go to Project Settings → Toolchain (or in Jira Software, navigate to the Development panel inside any issue)
2. Click Connect repository
3. Select GitHub from the provider list
4. Authorise JIRA to access the GitHub account or organisation
5. Select the repositories to connect
6. Click Save

Once connected, JIRA scans existing and new commits for issue keys. Developers do not need to change any workflow — they simply include the issue key (e.g., PROJ-204) in their commit messages as they normally write them.

Confluence Integration

Confluence is Atlassian's documentation and wiki tool. When connected to JIRA, teams can link Confluence pages directly to JIRA issues and view related documentation without leaving JIRA.

Key Confluence-JIRA Connections

Slack Integration

The JIRA Cloud app for Slack allows teams to receive notifications, create issues, and update issue fields without leaving the Slack workspace.

What the Slack Integration Allows

• Receive a Slack message when a JIRA issue is assigned, transitioned, or commented on
• Create a new JIRA issue using the /jira create slash command in Slack
• Preview JIRA issue details by pasting an issue link into a Slack message
• Subscribe a Slack channel to notifications from a specific JIRA project

Connecting Slack to JIRA

1. Install the JIRA Cloud app from the Slack App Directory
2. Type /jira connect in any Slack channel
3. Authorise the connection using the JIRA account credentials
4. Select the JIRA site to connect
5. Use /jira subscribe in a channel to receive project notifications there

Microsoft Teams Integration

The JIRA Cloud app for Microsoft Teams works similarly to the Slack integration. Teams members can receive JIRA notifications in a channel, respond to issues, and create new JIRA issues directly from the Teams interface.

CI/CD Tool Integrations

JIRA integrates with CI/CD pipelines to give teams real-time visibility into build and deployment status alongside their issues.

Issue: PROJ-310 — Add payment gateway

Development Panel inside the issue:
─────────────────────────────────────────────────
Branch     → feature/PROJ-310-payment-gateway
Commit     → 3 commits   [latest: 2h ago]
PR         → #47 — Open — 1 approval pending
Build      → GitHub Actions — ✔ Passing
Deployment → Staging — ✔ Deployed 1h ago
─────────────────────────────────────────────────

Atlassian Marketplace Apps

The Atlassian Marketplace hosts thousands of add-ons that extend JIRA's functionality. Some of the most widely used categories include:

Part 2 — JIRA Administration

JIRA administration involves managing the overall system — setting up projects correctly, controlling who can access what, configuring workflows and schemes, and maintaining healthy system performance. A JIRA administrator holds the highest level of configuration control in the platform.

JIRA Admin Roles

JIRA has two levels of administrative access:

User Management

Site Administrators manage all user accounts through the Atlassian Admin Console. The key tasks include:

• Inviting new users by email address
• Assigning product access (JIRA Software, JIRA Service Management, Confluence)
• Deactivating accounts when team members leave
• Organising users into groups for bulk permission management

User Groups

A user group is a collection of users that can be assigned permissions together. Instead of assigning permissions to 20 individual users, create a group called "Backend Team" and add all 20 users to it. Assign permissions to the group once — every member inherits those permissions automatically.

Group: Backend Team
Members: Ravi, Priya, Carlos, Meena, Jake

Permission applied to "Backend Team":
→ Browse Projects ✓
→ Create Issues ✓
→ Edit Issues ✓
→ Delete Issues ✗

All 5 members automatically receive the same access.

Schemes in JIRA Administration

A scheme is a reusable configuration template in JIRA. Instead of repeating the same configuration for every project, an admin creates a scheme once and applies it to multiple projects. When the scheme is updated, all projects using it are updated automatically.

The Six Core Schemes

Scheme Reuse Example:

Permission Scheme: "Standard Dev Team"
  Applied to: Project Alpha, Project Beta, Project Gamma

When the admin updates "Standard Dev Team" scheme:
→ Project Alpha gets the update ✓
→ Project Beta gets the update ✓
→ Project Gamma gets the update ✓

No need to update each project individually.

Project Configuration

Project Administrators manage settings for their specific project without requiring full site admin access. The key configuration areas include:

Project Details

• Project name, key, description, and avatar
• Project lead (the primary owner and contact)
• Project category (useful for organising large organisations with many projects)

Board Configuration

• Adding, removing, or renaming board columns
• Setting column constraints (minimum and maximum work-in-progress limits)
• Configuring swimlanes (grouping by assignee, epic, or priority)
• Setting quick filters on the board for faster issue filtering

Components and Versions

• Creating components to categorise issues by area (e.g., "Frontend", "Database", "API")
• Creating versions (releases) to group issues targeted for a specific release date
• Archiving completed versions after a release ships

Screens and Fields Administration

JIRA screens control which fields appear during different issue operations. There are three screen operations:

Admins can add or remove fields from each screen. For example, the "Create Issue" screen might only ask for Summary, Description, and Priority. The "Edit Issue" screen can show additional fields like Story Points, Components, and Fix Version.

Custom Fields

JIRA includes dozens of built-in fields, but teams often need to capture data that no built-in field covers. Custom fields solve this.

Creating a Custom Field

1. Go to Settings → Issues → Custom Fields
2. Click Add custom field
3. Choose the field type (text, number, date, dropdown, checkbox, user picker, etc.)
4. Name the field and set the options if applicable
5. Associate the field with one or more screens

Common Custom Field Types

Global Settings vs. Project Settings

Understanding the boundary between global and project-level settings prevents configuration conflicts and ensures consistent behaviour across the JIRA site.

┌────────────────────────────────────────────────────────────┐
│                   JIRA ADMINISTRATION                       │
├─────────────────────────┬──────────────────────────────────┤
│   GLOBAL SETTINGS       │   PROJECT SETTINGS               │
│   (Site Admin only)     │   (Project Admin)                │
├─────────────────────────┼──────────────────────────────────┤
│ • User management       │ • Board columns and swimlanes    │
│ • Groups and roles      │ • Components and versions        │
│ • Custom fields         │ • Project lead and details       │
│ • Global schemes        │ • Assign workflow scheme         │
│ • Issue types (global)  │ • Assign permission scheme       │
│ • System email settings │ • Quick filters                  │
│ • Marketplace apps      │ • Project-level automation       │
│ • Backup and restore    │ • Issue link types               │
└─────────────────────────┴──────────────────────────────────┘

Audit Log in Administration

JIRA maintains an admin-level Audit Log that records every configuration change made on the site. This is different from the Automation Audit Log. The admin audit log tracks changes like:

• Which user changed a permission scheme and when
• Which admin added or removed a user from a group
• When a workflow was modified and by whom
• When a project was created, archived, or deleted

The Audit Log is the primary tool for compliance and security review. Organisations that follow compliance frameworks like ISO 27001 or SOC 2 use the JIRA Audit Log to demonstrate accountability and access control records.

Backup and Restore

For JIRA Server and Data Center installations, admins can schedule regular backups and restore from backup files if data loss occurs. For JIRA Cloud, Atlassian manages infrastructure backups, but admins can export project data as a backup archive from Settings → System → Backup Manager.

Key Points

• Integrations connect JIRA to development, communication, and deployment tools so all data is visible in one place
• Including the JIRA issue key (e.g., PROJ-204) in commit messages automatically links code activity to the issue
• The Atlassian Marketplace extends JIRA with thousands of third-party apps for testing, reporting, and time tracking
• Schemes are reusable configuration templates — changes to a scheme apply instantly to all projects using it
• User groups simplify permission management for large teams
• Custom fields allow teams to capture project-specific data that built-in fields do not cover
• The Admin Audit Log provides a complete record of all configuration changes for compliance and security tracking
• Project Administrators control board and project-level settings; Site Administrators control global settings and user management