---
title: "Jira in pages"
description: "Put Jira issues anywhere in a page as live chips, cards or lists, change their status and assignee from the page, and turn a comment thread into an issue."
canonical_url: https://docs.markdrop.in/collaboration/jira-in-pages
last_updated: 2026-11-10
prerequisites: [/pages/overview, /integrations/jira]
site: "Markdrop Docs"
index: https://docs.markdrop.in/llms.txt
---

# Jira in pages

Jira issues can live anywhere in a page: in a sentence, as a card with their details, or as a live list from a project, a saved filter or a JQL query. People who are signed in and have connected their own Atlassian account see each issue's live status and can change it from the page. Everyone else sees the issue's key and title.

Jira in pages works with any Jira Cloud site your Atlassian account reaches. A workspace that's [connected to Jira](https://docs.markdrop.in/integrations/jira) also gets its site filled in for you, so `PAY-12` is enough.

## Three ways to show an issue

| Form | What readers see | Add it with |
| --- | --- | --- |
| **Chip**, inside text | The key and title, and the status for people whose Jira can open it. Select it to open the issue's card. | Paste a Jira link, type **/jira**, or type **@** and the key (for example **@PAY-12**) |
| **Card**, a block | Title, status, assignee, priority, type, due date, sprint and when it was last updated, with buttons to change them | **/Jira card**, or select a chip and choose **Show as a card** |
| **List**, a block | A table of issues, always current, with the status of each row ready to change | **/Jira list**, or one of the ready-made lists below |

![In a launch plan: the chip “PAY-1 Retry failed card payments, In Progress” inside a list item, and below the Risks paragraph a card for PAY-2 “Refund flow for annual plans”: status To Do, assignee Alex Chen, priority Medium, due Nov 15, updated Nov 9, with Comment and Edit.](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/chip-and-card.webp)

## Slash commands

Type **/jira** in a page to see every Jira command in the menu's **Jira** section. Keep typing to narrow it down, for example **/jira sprint** or **/bugs**.

| Command | What it adds |
| --- | --- |
| **/jira issue** | A chip. Search by key, link or words from the title. |
| **/jira card** | A card for one issue, with its status, assignee and actions. |
| **/jira list** | A live list from a project, a saved filter or a JQL query. |
| **/jira my issues** | A live list of open issues assigned to whoever is reading the page. Each reader sees their own. |
| **/jira sprint** | A live list of a project's current sprint. Choose the project. |
| **/jira bugs** | A live list of a project's open bugs, most urgent first. Choose the project. |
| **/jira recently updated** | A live list of a project's issues changed in the last 7 days. Choose the project. |
| **/jira epic** | Choose an epic: its card, and below it a live list of its child issues. |
| **/jira create** | A new issue, drafted for you to check, then its chip. |
| **/jira from selection** | The text on the line where you typed it becomes a new issue, and the text becomes the issue's chip. On an empty line, the block above is used. |

Every ready-made list is an ordinary Jira list with a JQL query, such as `assignee = currentUser() AND resolution = Unresolved ORDER BY updated DESC`. Select **Edit list** on it to change the query, the title or the columns.

### If you haven't connected Jira yet

The commands are there for everyone signed in who can edit the page. If your own Atlassian account isn't connected yet, choosing one asks you to **Connect Jira**. You come back to the page in Edit, and what you chose goes in where you typed it.

If the page's workspace isn't connected to a Jira site yet, the menu tells you so: a workspace admin connects it in **Settings › Workspaces › Integrations**. See [Jira](https://docs.markdrop.in/integrations/jira).

> **Note: On your workspace's own domain**
>
> On a page opened on your workspace's own domain, readers see its issues as usual, but Jira is added and changed from markdrop.in. Choosing a Jira command offers **Open on markdrop.in**: the page opens there in Edit, and what you chose goes in where you typed it.

### In a Markdown document

In the block editor of a Markdown document (**Preview**), **/jira issue**, **/jira create** and **/jira from selection** add the issue as a link, `PAY-12 · Title`, that opens it in Jira. Cards and live lists are page blocks.

### Paste a Jira link

Paste a link such as `https://acme.atlassian.net/browse/PAY-12` on its own and it becomes a chip straight away. To keep it a plain link, paste with ⌘ ⇧ V (Ctrl Shift V).

[Video: In the editor, after “Tracked in”, a pasted Jira link becomes the chip “WEB-2 Cookie banner for EU, To Do”; then typing @WEB-1 and Enter adds the chip “WEB-1 Pricing page copy, Done”. (0:07)](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/paste-link.mp4)

### Add a chip or a card

1. Type **/jira issue** (the chip) or **/jira card** in a page.
2. Search your Jira by key or by words from the title. With nothing typed, the picker lists issues assigned to you or reported by you.
3. Choose the issue, or paste its key or link.

To start a new issue right there, type **/jira create**, write what it's about and choose **Create**. Markdrop AI drafts the issue; you check every field, then it's created as you and its chip goes where you typed.

### Add a live list

1. Type **/jira list**.
2. Choose where the issues come from:
   - **Project**: every issue in a project, newest first. Enter its key, such as `PAY`.
   - **Saved filter**: a filter you saved in Jira. Enter its number, the one in the filter's address.
   - **JQL**: any Jira query, such as `project = PAY AND status != Done ORDER BY priority DESC`.
3. Optionally give it a title, choose its columns (status, assignee, priority, type, due date, sprint, updated) and how many issues to show per page.
4. Choose **Show issues**.

A list shows 25 issues at a time; **Load more** shows the next ones. Select **Edit list** on the block to change it.

![A live list titled Payments work, project = "PAY" ORDER BY updated DESC: PAY-1 Retry failed card payments, In Progress, Alex Chen, High, due Nov 7 in red; PAY-2 Refund flow for annual plans, To Do, Alex Chen, Medium, Nov 15; PAY-3 Invoice PDF footer, Blocked, Sam Lee, Medium.](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/list.webp)

> **Note: Each reader sees their own list**
>
> A list's query runs as the person reading the page, through their own Jira. Nobody sees an issue their Jira wouldn't show them, even if the person who wrote the query can see more. Readers can only run the lists saved on the page.
>
> When an issue changes in Jira, open pages with a list that could include it run the list again, each reader through their own Jira. Markdrop only tells the page to refresh. It doesn't send the issue or its details.

## Create an issue from text on the page

Select some text, then choose **Create Jira issue** in the toolbar. Markdrop AI drafts the issue from the text: summary, description, project, type, priority, assignee and due date. Change anything, then select **Create issue**. The issue is created as you, and the text you selected becomes the new issue's chip.

This needs the page to be in a workspace that's connected to Jira.

## Change an issue from the page

Open a chip (select it) or use a card or a list row. These changes are made in Jira **as you**, so Jira's own permissions decide what you can do:

- **Status.** Select the status to see every step your Jira workflow offers you, not just Done. When a step asks for more, such as a resolution, Markdrop asks you for it before moving the issue.
- **Assignee.** Search the people Jira lets you assign the issue to, or choose **Unassign**.
- **Comment.** Add a comment to the issue in Jira.
- **Edit.** Change the title, priority or due date.

If Jira refuses a change, Markdrop shows Jira's reason as it is, for example "Jira says you don't have permission to move PAY-12".

[Video: Alex opens the status of the PAY-3 card, Invoice PDF footer, which is Blocked; the menu lists To Do, In Progress, Done and Resolve, which asks for more. He chooses In Progress and the card updates. Then he chooses Comment, writes “Legal sent the copy.” and sends it to Jira. (0:11)](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/card-status.mp4)

[Video: A live list of Website issues: Alex opens the status of WEB-2 Cookie banner for EU and moves it from To Do to Done; the row updates and a toast says WEB-2 → Done. (0:08)](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/live-list.mp4)

Changes show for everyone reading the page within a few seconds. Each person's page reads the issue again through their own Jira, so nobody is sent details they couldn't see.

## Turn a comment thread into an issue

In a [comment thread](https://docs.markdrop.in/collaboration/comments), choose **Create Jira issue** on the thread. Markdrop AI drafts the issue from the discussion, you review every field, and it's created as you. The issue's description links back to the thread, and the thread shows the issue, with its live status, under its first comment.

[Video: On Sam's thread about screenshots for the help article, Alex chooses Create Jira issue. The dialog shows the drafted summary, description, project Payments, type Task and assignee; he chooses Create issue and the thread now shows PAY-4 with its status, To Do. (0:10)](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/thread-to-issue.mp4)

![The thread with its issue: Sam Lee asks who takes the screenshots for the help article, and under it PAY-4 “Screenshots for the new checkout help article” with its status, To Do.](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/thread-issue.webp)

You can also choose **Link a Jira issue** to connect a thread to an issue that already exists, or **Unlink the Jira issue**.

The two stay in step without surprises:

- Resolve the thread while the issue is still open, and the thread offers **Move to Done** in Jira.
- When the issue is Done in Jira and the thread is still open, the thread offers **Resolve discussion**.

## Who sees what

| Who | What they see |
| --- | --- |
| Signed in, Atlassian account connected, and their Jira can open the issue | Live status, assignee, priority, due date and sprint, and the buttons to change them |
| Signed in, Atlassian account connected, but their Jira can't open the issue | The key and title |
| Signed in, no Atlassian account connected | The key and title, and **Connect Jira** |
| Not signed in | The key and title, as a link to the issue in Jira |

![What a reader who isn't signed in sees: the chip shows only PAY-1 and its title, and the card shows PAY-2 and its title, with no status, assignee or dates.](https://docs.markdrop.in/docs-assets/collaboration/jira-in-pages/signed-out.webp)

The title readers see is the one saved when someone who can edit the page added the issue. It follows renames made in Jira. Lists show nothing to people without Jira, only **Connect Jira** or a note to sign in. Markdrop never asks Jira anything on behalf of someone who isn't signed in.

To connect your account, select **Connect Jira** on any chip, card or list, or go to **Settings › Integrations › Jira**.

## In exports and AI apps

Jira chips, cards and lists leave [exports](https://docs.markdrop.in/pages/export) as plain links: the key and title, linking to the issue in Jira, and a list as a link to its query in Jira. Your exported page reads well in any app.

In the page's Markdown they're written as:

```markdown
Blocked on :jira[PAY-12]{site=acme.atlassian.net} until Friday.

::jira{key=PAY-3 site=acme.atlassian.net}

::jira-list{jql="project = PAY AND status != Done" cols="status,assignee,due" limit=25 title="Open payments work"}
```

`site` is optional when the page's workspace is connected to Jira.

## For AI apps (MCP)

| Tool | What it does |
| --- | --- |
| `insert_jira` | Puts an issue on a page as a chip or a card, or adds a live list (JQL, a project or a saved filter), at the end or after a heading |
| `update_jira_issue` | Changes an issue as you: a workflow step by name (with the fields it needs), the assignee, a comment, the title, priority or due date |
| `list_jira_transitions` | The steps you can take on an issue now, and the fields each one needs |
| `create_jira_issue` | Drafts or creates an issue from an item or selected text; from selected text, that text becomes the issue's chip |
| `thread_to_jira` | Drafts or creates an issue from a comment thread and links the two; `put_chip` also puts the issue's chip right after the text the thread is about |

`get_page` lists the page's Jira chips, cards and lists as plain links. See [For AI apps](https://docs.markdrop.in/collaboration/for-ai-apps) and [MCP tools](https://docs.markdrop.in/ai/tools#jira).
