JIRA Integration

Complete guide to setting up JIRA Software or JIRA Service Management integration with SecureHive. The integration provides bidirectional issue synchronization, webhook support, and automated incident creation.

Prerequisites

A JIRA account (Cloud or Server/Data Center)
Admin access to your JIRA instance
Your SecureHive tenant ID

This integration supports both JIRA Software (Plan & Track) and JIRA Service Management (Support & Fix). The setup process is identical for both — they use the same API and authentication.

Choosing your JIRA product

Product	Issue types	Best for
JIRA Software	Task, Bug, Story, Epic	Tracking development work, technical issues, feature requests
JIRA Service Management	Incident, Service Request, Problem, Change Request	Security incidents, IT service requests, operational issues

Setting up your JIRA account

Create or access your JIRA instance

If you don’t have a JIRA account, sign up at atlassian.com/software/jira . For existing accounts, log in and confirm you have admin permissions.

For JIRA Software, your instance URL will be something like yourcompany.atlassian.net.

Create a project

Create a project in JIRA for SecureHive integration.

For JIRA Software: go to Projects → Create project, select Software, choose a template (Scrum, Kanban, etc.), enter a project name and key (e.g. SEC for Security), and click Create.

For JIRA Service Management: go to Projects → Create project, select Service Management → IT Service Management or Business Service Management, choose a template (e.g. “IT Service Desk”), enter a project name and key (e.g. ITSD), and click Create.

Get your project key

The project key is visible in the URL when viewing your project. For example, in https://yourcompany.atlassian.net/browse/SEC-123, the project key is SEC.

Save this key — you’ll need it when configuring the integration in SecureHive.

Identify available issue types

In the JIRA UI, issue types are called Work types (newer terminology), but in the API they are called Issue types. They refer to the same thing.

To find available types: go to your project in JIRA, click Create to start a new issue, and look at the Work type dropdown. Note the available options and save the exact name — you’ll need it when configuring the integration.

JIRA product	Recommended issue type	When to use
JIRA Software	`Task`	General security issues, compliance tasks
JIRA Software	`Bug`	Security vulnerabilities, technical defects
JIRA Service Management	`Incident`	Security incidents, operational issues
JIRA Service Management	`Service Request`	Policy requests, access requests

Creating an API token

Generate a token

JIRA uses API tokens for authentication instead of passwords. To generate one:

Log in to your JIRA instance
Click your profile picture in the top right corner
Select Account settings
In the left sidebar, click Security
Scroll to API tokens and click Create API token
Give it a label (e.g. “SecureHive Integration”)
Click Create

Copy the token immediately — you won’t be able to see it again.

Format your API credentials

For SecureHive, format your API token as email:token (no spaces). This combined string is what you’ll enter as the API Key in SecureHive.

Example: your.email@example.com:ATATT3xFfGF0a1b2c3d4e5f6...

Get your base URL

Your JIRA base URL is your instance URL without a trailing slash or any API path.

Deployment	Example
Cloud	`https://mycompany.atlassian.net`
Server / Data Center	`https://jira.mycompany.com`

Do not include /rest/api/3 or any other path suffix.

Configuring webhooks

You must create the integration in SecureHive first (see the next section) before you can get the webhook URL.

Get your SecureHive webhook URL

After creating the integration in SecureHive, the system generates a webhook URL automatically. To find it: go to Settings → Integrations → Service Management, find your integration in the list, and click the integration card or use the Edit button to view details. The Webhook URL is displayed in the integration details.

The URL format is: {API_BASE_URL}/integrations/service-management/webhooks/{your-tenant-id}

Create a webhook in JIRA

In JIRA, click Settings (gear icon) in the top right
Select System (Cloud) or Administration (Server/Data Center)
In the left sidebar under ADVANCED, click Webhooks
Click Create a webhook
Fill in the details: name it “SecureHive Integration”, set status to Enabled, and paste your SecureHive webhook URL
Under Events, select: Issue created, Issue updated, and optionally Issue deleted and Worklog updated
Leave Exclude body unchecked — SecureHive needs the full payload
Click Create

Configuring in SecureHive

Before starting, confirm you have: your JIRA base URL, project key, API token formatted as email:token, and your chosen issue type.

Navigate to integration settings

In SecureHive, expand the Administration section in the left sidebar, then expand Admin and click Integrations. You can also navigate directly to /s/{your-tenant}/settings/integrations/service-management.

Fill in the integration form

Field	Value
Platform Type	`JIRA`
Platform Name	A descriptive name (e.g. “JIRA ServiceDesk - Production”)
Base URL	Your JIRA instance URL (e.g. `https://yourcompany.atlassian.net`)
Authentication Type	`API_KEY`
API Key	Your formatted credential (`email:token`)

Configure project key and issue type

Field	Value
Project Key	Your JIRA project key (e.g. `ITSD` or `SEC`)
Issue Type	The exact issue type name from your project (e.g. `Incident` or `Task`)

The issue type name must match exactly (case-sensitive) what appears in your JIRA project.

Test the connection

After saving, use the Test Connection button to verify your credentials are correct, the API token has proper permissions, and the base URL is accessible.

If the test fails, check that the API token format is correct (email:token), the token hasn’t expired, your JIRA account has proper permissions, and the base URL is correct.

Activate the integration

Enable the Active toggle. The integration status should change to ACTIVE after successful configuration.

Verifying the integration

Test issue creation: Create a test issue in SecureHive. The issue should automatically sync to JIRA — check your JIRA project to verify.

Test webhook reception: Update an issue in JIRA that was synced from SecureHive. Check SecureHive to verify the webhook was received and the issue status updated.

Troubleshooting

Authentication failed — Verify the API token format is email:token with no spaces, the token hasn’t been revoked, and your JIRA account has proper permissions.

Project not found — Verify the project key is correct (case-sensitive), the project exists in your JIRA instance, and your account has access to the project.

Webhook not receiving events — Verify the webhook URL is correct in JIRA, webhook events are enabled, your SecureHive instance is accessible from the internet, and check SecureHive logs for errors.

Issue type not found — Verify the issue type name matches exactly (case-sensitive). Check available issue types in your JIRA project by going to Project Settings → Issue types.

To test the JIRA API connection directly, use:


curl -u "your.email@example.com:YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  https://yourcompany.atlassian.net/rest/api/3/myself

This should return your JIRA user information if the credentials are correct.

Security best practices

API token security: Never share your API token. Use a dedicated service account if possible. Rotate tokens periodically and revoke tokens that are no longer needed.

Webhook security: Use HTTPS for webhook URLs. Configure webhook secrets and monitor webhook logs for suspicious activity.

Permissions: Apply the principle of least privilege. Grant only necessary permissions to the integration account and regularly review and audit permissions.