Integrations
Jira
Comments as Jira issues with their screenshot and page, by hand or every new comment, with replies and edits following.
Turn a comment into a Jira issue, with its screenshot, its page and a link back to it. Send one from the comment's menu, or let every new comment in a project become an issue by itself. After that the issue keeps up: replies land on it as Jira comments, and when the comment's words or due date change, the issue changes too.
Jira is part of the Studio and Team plans and works with Jira Cloud. You find it on the Integrations page in the sidebar, under Issue tracking. To post comments in a channel instead, see Slack.
Connect Jira
On the Integrations page, click Connect next to Jira. Atlassian asks you to allow layernote on your Jira site; once you do, the window closes by itself. Then click Manage to pick your projects.
- The workspace owner and admins connect and manage Jira. Members see which site it goes to, and send comments from the comment's menu.
- The Atlassian account you connect with needs a Jira site. A layernote workspace connects to one site; its address is at the top of the Jira settings.
- Issues are made in the name of the person who connected. The Jira settings say who that is.
Per project
Under Per project, each project shows where its comments go: a Jira project key with how issues come in, or Off. Click a project to change it:
| Setting | What it does |
|---|---|
| Jira project | The Jira project its issues go to, or Off to keep the project out of Jira. |
| Issue type | Task to begin with, or any other type that Jira project has, such as Bug or Story. |
| Issues from | The comment menu: only the comments you send. Every new comment: each new comment becomes an issue by itself. |
Two projects can share one Jira project. Post replies on the issue, above the projects, decides whether replies follow in Jira.
Create an issue
In a project that goes to Jira, open a comment's ⋯ menu and click Create Jira issue in followed by the project key, such as WEB. The issue's key appears on the comment right away. A comment has one issue at most: once it has one, the menu item is gone.
With Every new comment, you don't need to click anything. That counts from the moment you switch it on: earlier comments go through the menu. Comments from reviewers on a share link and from Claude become issues too. When Claude places ten comments at once, Jira gets ten issues.
Reviewers on a share link don't see Jira. Only a comment gets an issue, never a reply.
What goes into the issue
- Summary: the comment's first line.
- Description: the comment's text, then where it is (the page, frame or file, and the device when it isn't desktop), the page's address, the element, who wrote it and its due date, and a link to open the comment in layernote.
- Screenshot: the spot, attached as soon as it is made. It can arrive a little after the issue.
- Due date: in Jira's own due date field, when the project's screen has one.
- Label:
layernote, so you can filter on it. - Link: the issue links back to the comment in layernote.
In layernote, the issue's key shows on the comment, in the comment list and on the card on the board. Click it to open the issue in Jira.
When the comment changes
| In layernote | In Jira |
|---|---|
| A reply | A comment on the issue, with who wrote it. Only while Post replies on the issue is on. |
| The text is edited | The description follows. The summary stays, in case someone renamed the issue in Jira. |
| The due date changes | The due date follows, also when it is cleared. |
| The comment is deleted | A note on the issue that it was deleted in layernote. The issue stays. |
It goes one way. Comments and status changes made in Jira don't come back to layernote, and resolving a comment in layernote doesn't close its issue. Priority and board column stay in layernote.
If Jira refuses a change, for instance because a field is required, the Jira settings show what it said.