Setting up a New Jira Connector for Remediation

Jira connectors for remediation are setup through the use of an Atlassian App that will create tickets in the right Jira project.

Get the required info from Delve

1) Contact Delve to activate your JIRA Cloud connector. You need to provide us with:

  • Your project key: the all-caps code used to represent a project, for example, EXPL (This is present in your URL if you're looking at the JIRA Kanban board).
  • The issue type remediation tasks should be (bug/task/story/etc.). See for the list of existing issue types.
  • An existing Delve User that will:
    • Act as the synchronization user between JIRA and Delve (you might need to login to authorize it).
    • Act as a fallback user to create the tasks in JIRA in case the currently logged Delve user doesn't exist on the JIRA side.

2) Once Delve confirms the integration is activate for your account:

  • Navigate to your connectors configuration in Delve at https://<YOUR INSTANCE>
  • Click on the "i" (info) icon on the line of your JIRA connector.
  • Follow the instructions:
    • Authenticate with the Delve user account identified in step 1)
    • Copy the Atlassian App URL for the next steps

Add the Delve App in Atlassian

You must work with an Atlassian Administrator in order to be able to add apps to your Jira instance that are not from the Jira Marketplace.

Navigate to your Atlassian Settings side panel.

Choose the Apps settings.

Click on Manage Apps.

Under User-installed apps, click Settings.

Select Enable development mode, then click Apply.

Click on Upload App.

In the modal that appears, enter the URL that you were provided by the Delve Team, then click Upload.

Set the Access Rights for the Delve users in JIRA

In order to be able to create tickets on behalf of Delve users in JIRA, the Delve users that exist in JIRA need to have the "Browse Users and Groups" privileges.

The first step is to add these users to a new specific JIRA group (or use an existing group such as "jira-users") and then navigate to your JIRA Global permissions page and to add the correct privileges for this group of users.


If the users don't have sufficient enough access rights, the connector will still create tasks in JIRA but they won't be created on behalf of the Delve users.

Configure Delve to Use this Connector

Find your unique connector app URL from Delve's API.

Log into Delve using your regular credentials and visit the following URL:


You should obtain the JSON information about your previously set up connectors, including their app URL:

{"items":[{"connectUrl":"https://<UUID>","family":"JIRA","id":"<UUID>","name":"JIRA Connector","status":"fail","statusUrl":"https://<UUID>"}]}

You can find out what the status of your connector is by visiting the following URL:


For instance if you have not completed the setup and authorized your Client ID to do API requests on your behalf, you will see the following "unusable credentials" status.

{"status": "fail", "details": {"monitor:status": [{"status": "fail", "monitor": "warden.monitor", "reason": "Unusable credentials"}, {"status": "pass", "monitor": "jira.monitor", "reason": null}]}}

Authorize your Client ID to do API requests on your behalf

The final step to activate your connector is to authorize your Client ID for a certain period of time to be able to do API calls on your behalf.

Once logged in Delve, you can start the authorization process by visiting the following URL (note the mandatory trailing slash).


Then just follow the regular API authorization mechanism, which should activate your connector.