Jira Browser Fetch

Use this skill when Jira API-token authentication fails or the organization uses Microsoft/SSO and the user wants Jira issues, Jira Software board backlogs, or JQL result sets archived into a local raw/wiki folder.

The bundled script opens/reuses Chrome with a dedicated profile, lets the user complete SSO once, extracts Jira cookies via Chrome DevTools, verifies they represent an authenticated Jira REST session, and fetches Jira REST/HTML/XML/attachments into a raw directory.

Safety

Never ask the user to paste Jira cookies or API tokens into chat.
Prefer the browser automation flow because secrets remain in the local Chrome profile.
Treat fetched issue data and attachments as potentially confidential.
Do not update/transition/edit Jira issues with this skill; it is read-only.

Script

bash

scripts/jira-browser-fetch.js ISSUE-KEY [options]

Important options:

bash

--server URL       Jira base URL, e.g. https://example.atlassian.net
--raw-dir DIR      folder where ISSUE-KEY/ directories are created
--connected        fetch connected/referenced tickets too
--depth N          recursion depth for connected tickets
--scan-text        find issue keys in JSON/XML/HTML text, not only formal Jira links
--jql JQL          search Jira with JQL and fetch all matching issues
--backlog URL|ID   fetch all issues from a Jira Software board backlog URL or board id
--assignee-me      fetch all issues assigned to current Jira user
--max-attachment-size S  skip attachment files larger than S (default 5mb; use unlimited to disable)
--prefix A,B,C     only follow keys with these project prefixes
--wait SEC         SSO/session wait timeout per issue
--skip-existing    skip issues that already have a valid raw/<KEY>/issue.json

Example User Requests

Use this skill for user requests like:

"Fetch Jira issue
```
PROJ-123
```
into
```
raw/
```
through my browser session."

"Archive this Jira backlog for my LLM wiki:

https://example.atlassian.net/jira/software/c/projects/ABC/boards/42/backlog?epics=visible

"Fetch all Jira issues matching this JQL into the wiki raw folder."
"Pull my assigned Jira issues without asking me for an API token."
"Fetch this ticket and all linked tickets, including attachments under the default size limit."

Shared Atlassian SSO Session

All five Atlassian skills (

jira-browser-fetch

jira-update

confluence-browser-fetch

confluence-update

bitbucket-browser-fetch

) default to the same Chrome profile (

~/.local/share/atlassian-browser-chrome

) and DevTools port (

). Log in once via any skill and the others reuse that session automatically — no env vars needed.

This is a separate Chrome window from any browser the user already has open. The script always launches its own profile with remote-debugging enabled; cookies from the user's regular Chrome are not read. The user logs in inside the window the script opens; that session is then reused by every Atlassian skill until it expires.

Reuse signal. When attaching to an existing session, the script prints

Reusing Chrome DevTools on port 9223

and (if the target tab is open)

Found existing tab for <host>

. When you see those lines, do not ask the user to re-SSO — the session is already valid.

If Chrome/Chromium is installed via Flatpak, Snap, or another non-PATH location, set

CHROME=/path/to/launcher

(or a wrapper script) so the script can find the binary.

Override with

ATLASSIAN_CHROME_PROFILE

and/or

ATLASSIAN_CHROME_DEBUG_PORT

to relocate the shared profile/port, or use skill-specific

*_CHROME_PROFILE

*_CHROME_DEBUG_PORT

env vars for isolation.

Typical Workflow

Identify raw directory.
Run the script and show the command first.
If Chrome opens (first run or expired session), ask the user to complete SSO in that window. On subsequent invocations the script reuses the session silently — see the Reuse signal above.
Verify saved files.

Example:

bash

scripts/jira-browser-fetch.js \
  SWING-4770 \
  --server https://example.atlassian.net \
  --raw-dir ./raw \
  --connected \
  --scan-text \
  --prefix SWING,SSD,EC \
  --depth 1

# Fetch requested issues plus everything assigned to current user:
scripts/jira-browser-fetch.js \
  SWING-4611 SWING-4621 \
  --server https://example.atlassian.net \
  --raw-dir ./raw \
  --assignee-me

# Fetch every issue currently visible in a Jira Software board backlog:
scripts/jira-browser-fetch.js \
  --server https://example.atlassian.net \
  --raw-dir ./raw \
  --backlog 'https://example.atlassian.net/jira/software/c/projects/ABC/boards/42/backlog?epics=visible'

Output Layout

For each issue:

text

raw/ISSUE-KEY/
├── issue.json           # Jira REST issue with renderedFields,names,schema,changelog
├── issue.html           # Browser issue page HTML
├── issue.xml            # Jira XML issue view
├── remotelinks.json     # Jira remote links endpoint
├── connected-keys.json  # Connected/referenced issue keys detected
├── metadata.json        # Fetch metadata
├── attachments.json     # Attachment manifest, including skipped large-file references
└── attachments/         # Downloaded attachments under max-size threshold

A run manifest is written to:

text

raw/jira-browser-fetch-run.json

Backlog fetches also write:

text

raw/jira-board-<board-id>-backlog.json

Installation / PATH

The skill can be used directly by path. Optionally install a convenience symlink:

bash

mkdir -p ~/.local/bin
ln -sf ~/.pi/agent/skills/jira-browser-fetch/scripts/jira-browser-fetch.js ~/.local/bin/jira-browser-fetch

Then use:

bash

jira-browser-fetch SWING-4770 --raw-dir ./raw --connected

References

Usage reference
Distribution guide

jira-browser-fetch

NPX Install

Tags

SKILL.md Content

Jira Browser Fetch

Safety

Script

Example User Requests

Shared Atlassian SSO Session

Typical Workflow

Output Layout

Installation / PATH

References