How to connect Jira to Layerdock

Once Jira is connected, every new pin becomes an issue in the project you choose, with the comment, screenshot, page, element and the reporter's browser laid out in the description. Moving the issue to Done resolves the pin.

Before you start

A Jira Cloud account that can create issues in the project you want. Jira Server and Data Center are not supported.

Connect it

1. Authorise

In Layerdock, go to Integrations → Jira → Connect a dock, choose the dock, then Continue to Jira. Atlassian asks which site to authorise and shows the access being requested. Approve it.

2. Pick a project and issue type

These are one choice, not two: an issue type only means anything inside a project, and Jira validates the pair together. Click Choose a projecton the dock's row and pick, for example, WEB — Website → Bug.

Jira connects switched off until you do this. An enabled Jira integration with no project would fail every single pin, so it only becomes deliverable at the moment you choose a target.

3. Test

Click Test. An issue should appear in the project within a few seconds.

If a project is missing from the picker

That is deliberate. Layerdock reads Jira's createmetawhen you connect, and hides any project whose create screen requires a custom field it cannot fill — Team, Component, Sprint, or whatever your admin has made mandatory.

If those projects were offered, Jira would reject everydelivery with a 400 and you would find out days later from an empty backlog. To use one, make the field optional on that project's create screen in Jira, or pick a different project.

Two-way sync

Jira Cloud webhooks carry no signature at all, so the secret rides in the URL and the webhook URL is itself a credential. Treat it like a password.

1. Jira → Settings → System → WebHooks → Create a WebHook
2. URL: https://www.layerdock.io/api/webhooks/jira?secret=YOUR_SECRET
3. Events: Issue → updated, and only that one

YOUR_SECRET is the value of JIRA_WEBHOOK_SECRET on the deployment. Ask whoever manages it; do not invent one here, since both sides must match.

A Jira status Layerdock does not recognise is ignored, never guessed at. Guessing would move a customer's real tickets, which is worse than doing nothing.

Good to know

The screenshot is embedded by link.Jira does have an attachment endpoint, and Layerdock tries it, but a task whose image silently vanished is worse than one carrying a link that always renders — so the link is always there regardless.

Only new pins create issues. Replies and status changes do not edit an existing issue.

If it stops working

Reconnect needed means Atlassian revoked the authorisation, or a refresh failed. Click Reconnecton that dock's row.

If it worked at first and stopped about an hour later, the app was registered without the offline_access scope, so no refresh token was ever issued. That is a deployment-side fix, not something you can change from Layerdock.

Want a chat channel instead? Connect Slack, or see all documentation.