LayerDock
Jira integration

Website feedback that lands in Jira as an issue.

A client clicks an element on the live site and types a comment. Layerdock files it in the Jira project you chose, with the screenshot and the technical context already in the description.

Setup guide
At a glance

What you get in Jira

A pin becomes
An issue, in the project and issue type you pick for that dock
The issue carries
The comment, a screenshot, the page URL, the element and its CSS selector, the viewport, and the reporter’s browser and OS
Status sync
Two-way: moving the issue to Done resolves the pin
Works with
Jira Cloud. Jira Server and Data Center are not supported
Connects by
Atlassian sign-in (OAuth). No API token to paste
Plans
Pro and Agency
Setup

Connect Jira in three steps

The Jira setup guide has every screen and what to do if something goes wrong.

  1. Step 1

    Authorise Atlassian

    From Integrations, choose Jira and the dock to connect. Atlassian shows the site and the access requested; approve it and you are back in Layerdock.

  2. Step 2

    Pick a project and issue type

    They are chosen together, for example WEB and Bug, because Jira validates the pair. The integration stays off until you pick, so no pin is ever sent nowhere.

  3. Step 3

    Send a test

    Press Test and an issue appears in the project within a few seconds. From then on every new pin on that dock is filed the same way.

Good to know

How it behaves

One Jira project per dock

Each dock connects on its own, so each client site can file into its own project. An agency with eight clients does not end up with one mixed backlog.

Projects that would reject issues are hidden

When you connect, Layerdock checks each project’s create screen. A project that requires a custom field it cannot fill (Team, Component, Sprint) is left out of the picker, instead of failing every delivery later.

Unknown statuses are ignored, never guessed

Status changes coming back from Jira only act on statuses Layerdock recognises. Guessing would move a real ticket, which is worse than doing nothing.

New pins create issues; replies do not edit them

A reply or a status change in Layerdock does not rewrite an existing issue, so a ticket is never changed under the person working on it.

Ready when you are

Make the next
website review easier.

Give your team and clients one clear place to see the issue, capture the context, and share the fix.

Explore the tools
FAQs

Frequently asked questions

What to know before connecting Jira.

Does Layerdock work with Jira Server or Data Center?

No. The integration is for Jira Cloud only.

Do my clients need a Jira account to report something?

No. Clients open a review link, type a name and click the page. They never see Jira; your team sees the issue.

Is the screenshot attached to the Jira issue?

The screenshot is always embedded in the description by link, so it renders even if an upload fails. Layerdock also tries Jira’s attachment endpoint.

Why is one of my Jira projects missing from the picker?

Its create screen requires a custom field Layerdock cannot fill. Make that field optional on the project’s create screen in Jira, or choose another project.

Which Layerdock plans include integrations?

Pro ($19/mo) and Agency ($69/mo), both per workspace with unlimited reviewers. The Free plan does not include outbound integrations.