# Working With Jira Web

> Navigates JIRA for ticket operations. Primary: Atlassian MCP for CRUD. Fallback: Browser for visual verification. Triggers: JIRA, create ticket, edit ticket, link issues, JQL, fix version.

- **Type:** Skill
- **Install:** `agentstack add skill-quatico-solutions-agent-skills-working-with-jira-web`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [quatico-solutions](https://agentstack.voostack.com/s/quatico-solutions)
- **Installs:** 0
- **Category:** [Web & Browser](https://agentstack.voostack.com/c/web-and-browser)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [quatico-solutions](https://github.com/quatico-solutions)
- **Source:** https://github.com/quatico-solutions/agent-skills/tree/main/skills/working-with-jira-web

## Install

```sh
agentstack add skill-quatico-solutions-agent-skills-working-with-jira-web
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Working with JIRA

This skill covers JIRA ticket operations with two approaches:
- **Atlassian MCP** (primary) — fast, reliable API access
- **Browser automation** (fallback) — for visual verification or missing API features

---

## Tool Selection Decision Tree

```
Need to interact with JIRA?
├── Create/Read/Update ticket? → Atlassian MCP
├── Search tickets (JQL)? → Atlassian MCP
├── Add comment? → Atlassian MCP
├── Visual verification needed? → Browser automation
├── Feature not in API? → Browser automation
└── Debug why MCP failed? → Browser automation
```

| Operation | Recommended Tool | Why |
|-----------|------------------|-----|
| Create ticket | MCP `createJiraIssue` | Single API call, markdown description |
| Update description | MCP `editJiraIssue` | Markdown input, instant update |
| Read ticket | MCP `getJiraIssue` | Full data, no UI parsing |
| Search (JQL) | MCP `searchJiraIssuesUsingJql` | Structured results |
| Add comment | MCP `addCommentToJiraIssue` | Markdown, no WYSIWYG |
| Link tickets | MCP or Browser | MCP limited, browser more flexible |
| Visual verification | Browser | See rendered result |

---

## Atlassian MCP (Primary)

### Authentication

1. Run `/mcp` in Claude Code
2. Select **atlassian** from the list
3. Complete OAuth flow in browser
4. Sessions expire periodically — re-run `/mcp` if you get auth errors

### Key Tools

| Tool | Purpose |
|------|---------|
| `getJiraIssue` | Fetch ticket details |
| `editJiraIssue` | Update ticket fields (description accepts markdown!) |
| `createJiraIssue` | Create new ticket |
| `addCommentToJiraIssue` | Add comment (markdown) |
| `searchJiraIssuesUsingJql` | Search using JQL |
| `getTransitionsForJiraIssue` | Get available status transitions |
| `transitionJiraIssue` | Change ticket status |

### CloudId Discovery

Most tools require `cloudId`. Get it from search results or use `getAccessibleAtlassianResources`.

### Example: Update Description

```typescript
mcp__plugin_atlassian_atlassian__editJiraIssue({
  cloudId: "your-cloud-id",
  issueIdOrKey: "EWZREL-123",
  fields: {
    description: "## Overview\n\nThis ticket tracks...\n\n- Item 1\n- Item 2\n\n### Technical Details\n\n```\ncode block here\n```"
  }
})
```

**Key insight**: The `description` field accepts **markdown**, not wiki markup or ADF. The API converts it automatically.

### Example: Create Ticket

```typescript
mcp__plugin_atlassian_atlassian__createJiraIssue({
  cloudId: "your-cloud-id",
  projectKey: "EWZREL",
  issueTypeName: "Bug",
  summary: "Button not working on mobile",
  description: "## Steps to Reproduce\n\n1. Open on mobile\n2. Tap button\n3. Nothing happens"
})
```

### Example: Search with JQL

```typescript
mcp__plugin_atlassian_atlassian__searchJiraIssuesUsingJql({
  cloudId: "your-cloud-id",
  jql: "project = EWZREL AND fixVersion = '1.7' ORDER BY created DESC",
  maxResults: 50
})
```

### MCP vs Browser Comparison

| Aspect | MCP API | Browser Automation |
|--------|---------|-------------------|
| Description update | 1 API call | ~20+ interactions |
| Input format | Markdown | WYSIWYG toolbar |
| Focus issues | None | Constant problem |
| Keyboard traps | None | `L`, `@` shortcuts |
| Reliability | ~100% | ~60% |
| Speed | Goal
Description with formatting and links

  ColumnValue
  Row 1Data

`;
editor.dispatchEvent(new Event('input', { bubbles: true }));
```

**When to use:**
- Complex descriptions with tables, nested lists, multiple headings
- Content with many links (Bitbucket, external URLs)
- Avoiding focus-loss issues during multi-section entry

**Why this works:**
- JIRA uses ProseMirror editor under the hood
- Direct HTML injection bypasses WYSIWYG interaction fragility
- `input` event dispatch triggers JIRA's state management

---

## Workflow Recommendations

### For Ticket Updates

1. **First choice**: Use `editJiraIssue` MCP tool with markdown
2. **If MCP fails**: Check authentication (`/mcp` → atlassian)
3. **Visual check needed**: Open in browser to verify rendering

### For New Tickets

1. **First choice**: Use `createJiraIssue` MCP tool
2. **After creation**: Optionally open in browser to verify/add features not in API

### For Searches

Always use `searchJiraIssuesUsingJql` — structured data, no HTML parsing needed.

---

## Session Cleanup

```
- [ ] Task complete
- [ ] If browser was used: Navigate to about:blank
- [ ] Inform user of completion
```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [quatico-solutions](https://github.com/quatico-solutions)
- **Source:** [quatico-solutions/agent-skills](https://github.com/quatico-solutions/agent-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-quatico-solutions-agent-skills-working-with-jira-web
- Seller: https://agentstack.voostack.com/s/quatico-solutions
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.