Skip to content

Work tracking

Connect a Jira site through a service account so Dave can sync issues and comment on them as itself.

Jira can act as a request provider: issues become requests, and Dave publishes updates back as comments.

Dave connects through a Jira service account, so its comments, issues, and status changes show as Dave rather than as the person who connected it. Setup has two parts: an organization admin creates the service account, then you connect it in Dave and authorize Jira once so Dave can receive issue updates.

You need to be an organization admin in Atlassian Administration. Service accounts are available when your organization uses centralized user management; free plans include 5, and Atlassian Guard raises the limit.

  1. Go to admin.atlassian.com → Directory → Service accounts → Create a service account.

  2. Name it — this is the name shown on Dave’s comments. Names need at least 6 characters, e.g. Dave.io.

  3. On Select app roles, give Jira on your site the User role. Leave every other app at None.

  4. Open the new service account → Create credentials → OAuth 2.0.

  5. Select the service account scopes, then Create.

  6. Keep the page open. The Client ID and Client secret are shown once, at creation. Dave stores the secret encrypted and never shows it again.

  7. Grant the service account the project permissions on the projects Dave syncs.

  1. In Dave, go to Integrations → Add integration → Jira.

  2. Paste the Client ID and Client secret, then choose Connect Jira. A popup opens on Atlassian.

  3. Choose the site the service account belongs to and approve Dave. Most sites require a site administrator, in which case your approval becomes a request.

  4. Dave checks that the service account can reach that site, then marks the connection Active.

  5. Configure Request routing to tell Dave which issues to treat as requests.

Dave connects to one Jira site per workspace.

Dave uses two identities on the same site:

  • The service account does everything Dave reads and writes: creating and updating issues, transitioning them, posting comments, searching issues, and loading the projects, issue types, statuses, and labels shown in Request routing.
  • The person who approved the popup owns Dave’s webhooks: Dave registers, renews (every 30 days), and deletes them with that grant. Dave’s health check also uses both identities, so revoking either one breaks the connection.

To set it up you need:

  • An Atlassian organization admin to create the service account and its credential.
  • A Jira user who can approve apps on the site — usually a site admin.

Select these on the service account’s OAuth 2.0 credential:

read:jira-work
write:jira-work
read:jira-user

Give the service account these on every project Dave syncs:

Browse projects
Create issues
Edit issues
Add comments
Transition issues

The popup asks the approving user for these. You do not select them by hand:

read:jira-work
write:jira-work
read:jira-user
manage:jira-webhook
offline_access
  • Service account and its credential: admin.atlassian.com → Directory → Service accounts → the account. Revoke the credential there, or delete the account.
  • The site-wide app grant: admin.atlassian.com → Apps → Sites → your site → Connected apps.
  • The approving user’s own grant: that user opens id.atlassian.com → Account settings → Connected apps.

Disconnect in Dave deletes every webhook Dave registered on the site and stops all syncing. It does not revoke the popup grant or the service account credential — remove those in Atlassian too if you are not reconnecting.

Switch an existing connection to a service account

Section titled “Switch an existing connection to a service account”

Connections made before service accounts keep working, but Dave’s comments show as the person who connected Jira. To switch:

  1. Create the service account.

  2. In Dave, open the Jira connection → Disconnect.

  3. Connect again with the new credentials, choosing the same site.

Your request routing is restored when the connection is active again. Jira changes made between disconnecting and reconnecting are not synced.

  1. In Jira, note the project whose issues should become requests, the issue type Dave should create (usually Task or Bug), and the project’s statuses under Project settings → Workflows.

  2. In Dave, open the connection → Request routing.

  3. Pick the Site, Project and Issue type, plus Labels if you are filtering. The Site dropdown only lists sites this connection was granted. Jira only lists labels already used on an issue, and a new one can take a couple of minutes to appear.

  4. Map each Jira status to a Dave request status, then Save changes.

Comments on the issue flow into the request, and Dave posts updates back as issue comments.

Import tickets lists matching issues Dave is not tracking yet and opens a request for each you select.

The connection fails after approving the popup. Dave could not reach the site with the service account. Check that you chose the site the service account belongs to, that the service account has the User role for Jira on that site, and that the credential has the service account scopes. A credential created moments ago can take a minute to start working — retry with Resume setup.

Jira rejected the credentials. The client ID or secret is wrong, or the credential was revoked. Create a new credential on the same service account and connect again.

Issue updates stopped arriving. The popup grant was revoked, or the person who approved it left, so Dave can no longer renew its webhooks. Disconnect and connect again.