Jira

Overview

A Jira source allows Inkeep to ingest tickets from your Jira instance.

Setup Requirements

OAuth Authorization

When you create a Jira source, you will be redirected to an OAuth flow. Please ensure that you have admin access to the Jira instance.

Authorization Process:

1. Create a new Jira source in your Inkeep dashboard
2. You will be redirected to Atlassian's authorization page
3. Sign in to your Atlassian account if prompted
4. Review the permissions requested by Inkeep
5. Authorize access to your Jira instance
6. Complete the OAuth flow and return to Inkeep

User vs Service Accounts

By default, the Atlassian OAuth connection happens at the user level (so the read permissions are tied to what the user has access to and what is selected during the OAuth redirect). A pattern that some customers use is to create a user account that represents the connecting service, e.g. a user named "Inkeep Connector". This allows use of Atlassian's permissioning and RBAC system, and doesn't tie the connection to the status of a single employee.

Filtering

If would like certain ticket labels, projects, or statuses to be excluded from the source please contact the Inkeep team through Slack or email at sources@inkeep.com.