Skip to main content

​
JIRA OAuth App

Leen uses OAuth 2.0 for secure authentication with JIRA. Leen’s pre-configured OAuth app enables quick setup and handles the OAuth flow and token management automatically.

​
Required Permissions

The JIRA OAuth app requires the following scopes:
ScopePurpose
read:jira-workRead JIRA projects, issues, comments, and attachments
write:jira-workWrite access for passthrough endpoint operations
read:jira-userRead user information and groups
manage:jira-configurationRead users within groups
offline_accessEnable refresh tokens for long-lived access

​
Onboarding

1

Create JIRA Connection

With your Leen API Key and your organization ID, make an API request to create a new JIRA connection. More information can be found on the API Reference page.
{
  "vendor": "JIRA"
}
The response will look like this:
{
  "id": "c54de187-df62-4e95-b10f-0ab53b095d9d",
  "vendor": "JIRA",
  "refresh_interval_secs": 21600,
  "timeout_secs": 1800,
  "organization_id": "fbd8b095-3c39-4137-9478-c32308444202",
  "oauth2_authorize_url": "https://auth.atlassian.com/authorize?client_id=..."
}
You can optionally filter projects and provide custom mappings:
{
  "vendor": "JIRA",
  "options": {
    "project_keys_filter": ["PROJ1", "ENG", "SEC"],
    "priority_mapping": {
      "Highest": "CRITICAL",
      "High": "HIGH",
      "Medium": "MEDIUM",
      "Low": "LOW",
      "Lowest": "INFORMATIONAL"
    },
    "status_mapping": {
      "To Do": "TODO",
      "In Progress": "IN_PROGRESS",
      "Done": "CLOSED"
    }
  }
}
2

Authorize JIRA Access

Open the oauth2_authorize_url from the previous step in a browser. This will prompt you to authorize Leen to access your JIRA resources.
  1. Log in to your Atlassian account
  2. Select your JIRA site from the list
  3. Review the requested permissions
  4. Click Accept to grant access Jira-authorize
Once authorized, you will be redirected to Leen with a successful connection confirmation.Jira-successful-connection

​
Connection Options

​
Project Filter

You can optionally filter which JIRA projects to sync: 
{
  "project_keys_filter": ["PROJ1", "PROJ2", "ENG"]
}
Note: If not specified, all accessible projects will be synced.

​
Custom Priority Mapping

You can provide custom mappings from JIRA priorities to standardized ITSM priority values: 
{
  "priority_mapping": [
    {
      "Highest": "CRITICAL"
    },
    {
      "High": "HIGH"
    },
    {
      "Medium": "MEDIUM"
    },
    {
      "Low": "LOW"
    },
    {
      "Lowest": "INFORMATIONAL"
    },
    {
      "Parked": "INFORMATIONAL"
    }
  ],
}
Valid ITSM Priority Values:
  • CRITICAL - Highest priority, blockers, emergencies
  • HIGH - High priority, major issues
  • MEDIUM - Medium or normal priority
  • LOW - Low priority, minor issues
  • INFORMATIONAL - Lowest priority
  • UNKNOWN - Unmapped priorities
If not provided, Leen will auto-generate mappings based on priority names and keywords.

​
Custom Status Mapping

You can provide custom mappings from JIRA statuses to standardized ITSM status values: 
{
  "status_mapping": [
    {
      "To Do": "TODO"
    },
    {
      "In Progress": "IN_PROGRESS"
    },
    {
      "Done": "CLOSED"
    }
  ]
}
Valid ITSM Status Values:
  • OPEN - Newly opened
  • TODO - In backlog
  • IN_PROGRESS - Actively being worked on
  • IN_REVIEW - Under review
  • BLOCKED - Blocked or on hold
  • PENDING - Pending validation or testing
  • RESOLVED - Resolved, awaiting closure
  • CLOSED - Completed and closed
  • CANCELLED - Cancelled or rejected
  • UNKNOWN - Unmapped statuses
If not provided, Leen will auto-generate mappings based on status names, keywords, and JIRA status categories.