### Triage Workflow Examples

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/SKILL.md

Examples demonstrating the interaction flow for identifying duplicates and creating new issues with related context.

```text
Triage this error: "Connection timeout error when users try to login on iOS app"
```

```text
✅ Comment added to PROJ-456

Your iOS-specific error details have been added to the existing issue.
The assignee will be notified.
```

```text
Error: NullPointerException in PaymentProcessor.processRefund() at line 245
Stack trace: [full stack trace]
```

```text
✅ New Issue Created

PROJ-890 - Payment API: NullPointerException in refund processing
https://yoursite.atlassian.net/browse/PROJ-890

References related issue PROJ-789 for context.
```

--------------------------------

### Example: Clear Documentation Available

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

This example demonstrates synthesizing information from multiple sources (Confluence and Jira) to provide a comprehensive answer about 'Stratus minions'. It includes key characteristics, architecture, and implementation notes.

```text
Stratus minions are background worker processes that handle asynchronous task 
processing in the Stratus system.

**Key Characteristics:**
- Run independently from web servers
- Process jobs from a Redis queue
- Can be scaled horizontally for increased throughput
- Handle tasks like email sending, report generation, and data processing

**Architecture:**
According to the Stratus Architecture documentation, minions follow a 
worker-queue pattern where:
1. Web application enqueues tasks
2. Minions poll the queue for work
3. Tasks are processed asynchronously
4. Results are stored in the database

**Implementation Notes:**
From Jira ticket PROJ-203, the current deployment runs 5 minion instances, 
with plans to scale to 10 for handling increased load.

## Sources
- [Stratus Architecture Guide](link)
- [PROJ-203](link) - Minion scaling implementation
```

--------------------------------

### Optional Action Patterns

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example format for tasks that are not strictly required.

```text
Sarah could create a report if needed
Mike might review the code
```

--------------------------------

### Example: Conflicting Information

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

This example illustrates how to present conflicting information found in documentation and actual behavior. It clearly states the discrepancy, provides details from both sources, and offers a recommendation.

```text
There is a discrepancy between documented and actual behavior:

**Official Documentation** (Security Guidelines):
Session timeout is configured for 30 minutes of inactivity.

**Actual Behavior** (PROJ-456, reported Oct 2023):
Users are being logged out after 15 minutes due to a load balancer configuration 
that overrides the application setting.

**Current Status:**
The engineering team is aware of this issue. The load balancer timeout needs to 
be adjusted to match the application setting. No fix timeline has been set.

**Recommendation:** Plan for 15-minute timeout until this is resolved.

## Sources
- [Security Guidelines](link) - Official documentation
- [PROJ-456](link) - Timeout discrepancy bug report
```

--------------------------------

### Example Acceptance Criteria

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Examples of specific and testable acceptance criteria for user stories.

```text
API returns 201 status on successful user creation
```

```text
Password must be at least 8 characters and hashed with bcrypt
```

```text
Login form validates email format before submission
```

--------------------------------

### Complete Citation Section Example

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

An example of a complete citation section, including Confluence pages, Jira issues, and additional resources.

```text
## Sources

**Confluence Documentation:**
- [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345)
- [Minion Configuration](https://yoursite.atlassian.net/wiki/spaces/DEVOPS/pages/67890)

**Jira Issues:**
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization

**Additional Resources:**
- [Internal architecture doc link if found]
```

--------------------------------

### Example Epic Creation Response

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Expected JSON response format after successfully creating an Epic.

```json
{
  "key": "PROJ-123",
  "id": "10001",
  "self": "https://yoursite.atlassian.net/rest/api/3/issue/10001"
}
```

--------------------------------

### Example Parsing Output

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Demonstration of how raw meeting notes are parsed into structured assignee and task data.

```text
# Product Planning - Dec 3

Action Items:
- @Sarah to create user stories for chat feature
- Mike will update the architecture doc
- Lisa: review and approve design mockups
```

```text
1. Assignee: Sarah
   Task: Create user stories for chat feature
   Context: Product Planning meeting - Dec 3

2. Assignee: Mike
   Task: Update the architecture doc
   Context: Product Planning meeting - Dec 3

3. Assignee: Lisa
   Task: Review and approve design mockups
   Context: Product Planning meeting - Dec 3
```

--------------------------------

### Group Action Patterns

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example format for tasks assigned to multiple people or teams.

```text
Everyone to review the document
Team to provide feedback
```

--------------------------------

### Delegated Action Patterns

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example format for tasks where one person requests another to perform an action.

```text
John will ask Sarah to create the report
```

--------------------------------

### Task Pattern Validation Examples

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Examples used to validate pattern matching logic for task extraction.

```text
✅ @john to update tests
✅ Sarah will write docs
✅ Mike: review code
✅ TODO: Deploy (Lisa)
✅ Action: John - fix bug

⚠️ Maybe John can help?
⚠️ Documentation needs work
⚠️ We should test this

❌ John mentioned testing
❌ Tests were updated
❌ Someone needs to deploy
```

--------------------------------

### Example: Multiple Sources Agree

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Demonstrates synthesizing information when multiple sources provide consistent details. Use this pattern to build a cohesive answer.

```text
Stratus minions are background worker processes that handle async tasks.

According to the Confluence documentation, they process jobs from the queue and 
can be scaled horizontally. This is confirmed by several Jira tickets (PROJ-145, 
PROJ-203) which discuss minion configuration and scaling strategies.
```

--------------------------------

### Example: Incomplete Information

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Provides a template for acknowledging when information is incomplete based on available sources and suggests next steps for the user.

```text
Based on available documentation:

[What we know about deployment process from Confluence and Jira]

However, I couldn't find information about:
- Rollback procedures
- Database migration handling

You may want to check with the DevOps team or search for additional documentation.
```

--------------------------------

### Detect Urgent Priority Tasks

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example format for identifying high-priority tasks.

```text
URGENT: John to update docs
HIGH PRIORITY: Sarah to create report
ASAP: Mike to review code
```

--------------------------------

### Handle Conditional Actions

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example of an action item with a condition. Include the condition in the task description.

```text
John to update docs if approved
Sarah will create report pending review
```

--------------------------------

### Handle Time-Bound Actions

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example of an action item with a deadline. Extract the deadline and include it in the task description or use a due date field.

```text
John to update docs by EOD
Sarah will finish report by Friday
Mike to review before next meeting
```

--------------------------------

### Mixed Formats Task Creation Example

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Illustrates handling a mix of action items with and without assignees. The system prompts the user to decide whether to create all tasks or only those with assignees.

```plaintext
Product Review Meeting

Discussed new features and priorities.

Follow-ups:
- Sarah will draft the PRD
- Mike: implement API changes
- TODO: Review security audit (Lisa)
- Update stakeholders on timeline
```

```plaintext
I found 4 items (3 with assignees, 1 without)

Found 3 with assignees, 1 without. Create all or only assigned?

All, make the last one unassigned
```

--------------------------------

### Detect Low Priority Tasks

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example format for identifying tasks with lower urgency.

```text
If time: John to update docs
Nice to have: Sarah create report
Eventually: Mike review code
```

--------------------------------

### Example: Conflicting Information

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Shows how to present conflicting information from different sources, highlighting the discrepancy and noting the current reality versus documentation.

```text
There is conflicting information about the authentication timeout:

- **Official Documentation** (Confluence) states: 30-minute session timeout
- **Implementation Reality** (Jira PROJ-456, filed Oct 2023): Actual timeout is 
  15 minutes due to load balancer configuration
- **Status:** Engineering team aware, fix planned but no timeline yet

Current behavior: Expect 15-minute timeout despite docs saying 30 minutes.
```

--------------------------------

### Example: Sources Provide Different Aspects

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Illustrates combining information from different sources that cover distinct aspects of a topic. Clearly delineate information from each source.

```text
The billing system has two main components:

**Payment Processing** (from Confluence "Billing Architecture" page)
- Handles credit card transactions
- Integrates with Stripe API
- Runs nightly reconciliation

**Invoice Generation** (from Jira PROJ-189)
- Creates monthly invoices
- Note: Currently has a bug where tax calculation fails for EU customers
- Fix planned for Q1 2024
```

--------------------------------

### Example Summary of Created Tickets

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

A comprehensive summary of created tickets, including Epic and individual implementation tickets with links.

```text
✅ Backlog created successfully!

**Epic:** PROJ-123 - User Authentication System
https://yoursite.atlassian.net/browse/PROJ-123

**Implementation Tickets (7):**

1. PROJ-124 - Design authentication database schema
   https://yoursite.atlassian.net/browse/PROJ-124

2. PROJ-125 - Implement user registration API endpoint
   https://yoursite.atlassian.net/browse/PROJ-125

3. PROJ-126 - Implement user login API endpoint
   https://yoursite.atlassian.net/browse/PROJ-126

4. PROJ-127 - Build login form UI components
   https://yoursite.atlassian.net/browse/PROJ-127

5. PROJ-128 - Build registration form UI components
   https://yoursite.atlassian.net/browse/PROJ-128

6. PROJ-129 - Add authentication integration to existing features
   https://yoursite.atlassian.net/browse/PROJ-129

7. PROJ-130 - Write authentication tests and documentation
   https://yoursite.atlassian.net/browse/PROJ-130

**Source:** https://yoursite.atlassian.net/wiki/spaces/SPECS/pages/123456

**Next Steps:**
- Review tickets in Jira for accuracy and completeness
- Assign tickets to team members
- Estimate story points if your team uses them
- Add any additional labels or custom field values
- Schedule work for the upcoming sprint
```

--------------------------------

### Simple @Mentions Task Creation

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Example demonstrating the process of parsing simple @mentions in action items, looking up user IDs, and creating Jira tasks with assigned users.

```plaintext
Team Sync - Dec 3, 2025

Action Items:
- @Sarah to create user stories for chat feature
- @Mike will update the architecture doc
- @Lisa should review design mockups
```

```plaintext
✅ Created 3 tasks in PROJ:

1. PROJ-100 - Create user stories for chat feature
   Assigned to: Sarah Johnson
   
2. PROJ-101 - Update the architecture doc
   Assigned to: Mike Chen
   
3. PROJ-102 - Review design mockups
   Assigned to: Lisa Park
```

--------------------------------

### Extract Related Information for Context

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Examples of how related information like projects, context, or decisions might be presented.

```text
Related to: [project/epic/initiative]
Context: [background info]
Decision: [relevant decision]
```

--------------------------------

### Handle Multiple Assignees in Action Items

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Example of how to represent action items assigned to multiple people. Consider creating separate tasks or including all names in the description.

```text
John and Sarah to update documentation
Mike, Lisa to review PR
```

--------------------------------

### Name Lookup Issue Resolution Example

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Demonstrates how the system handles ambiguity when looking up an assignee's name, presenting multiple possibilities to the user for clarification before task creation.

```plaintext
Sprint Planning

Action Items:
- @John to update tests
- @Sarah to refactor code
```

```plaintext
Parse → 2 action items
Lookup "John" → Found 3 Johns!

Which John? (John Smith, John Doe, John Wilson)

John Smith
```

--------------------------------

### Query for Current Sprint Overview

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Get a comprehensive overview of issues within the current sprint, including their status and recent updates, ordered by priority and update time. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND status IN ("To Do", "In Progress", "In Review", "Done") AND updated >= -7d ORDER BY priority DESC, updated DESC
```

--------------------------------

### Identify Discussion Notes (Anti-Pattern)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

These examples represent discussions, not action items, as they lack specific assignments.

```text
John mentioned the documentation needs updating
Sarah suggested we create a report
Mike talked about reviewing the code
```

--------------------------------

### Best Meeting Notes Format Example

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Provides a recommended format for meeting notes to ensure clear identification of action items, including title, date, attendees, decisions, and action items with @mentions.

```plaintext
# Meeting Title - Date

Attendees: [Names]

## Decisions
[What was decided]

## Action Items
- @FullName to [specific task with context]
- @AnotherPerson will [specific task with context]
- etc.
```

--------------------------------

### Identify Past Actions (Anti-Pattern)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

These examples are in the past tense and indicate completed actions, not current action items.

```text
John updated the documentation
Sarah created the report
Mike reviewed the code
```

--------------------------------

### Extract Meeting Metadata

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Examples of meeting metadata formats to extract title, date, and potentially attendees.

```text
# [Meeting Title] - [Date]
Meeting: [Title]
Date: [Date]
Subject: [Title]
```

--------------------------------

### Create Jira Issue With Additional Fields

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Example of how to include custom required fields when creating a Jira issue.

```javascript
additional_fields={
  "priority": {"name": "High"}
}
```

--------------------------------

### Bullet List Parsing Example

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Demonstrates how bullet points are parsed to identify assignees and tasks. Assignees are typically found before a colon or hyphen, followed by the task description.

```plaintext
- John: update documentation
- Sarah - create the report
* Mike will review PR #123
```

--------------------------------

### Handle Nicknames or Short Forms for Assignees

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Examples of less common assignee name formats that may require user clarification or multiple lookup attempts.

```text
@SJ to create report
Sara (no h) will create report
```

--------------------------------

### Get Visible Jira Projects

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Use `getVisibleJiraProjects` to retrieve a list of available Jira projects for issue creation when the user is unsure of the project key. The `action` parameter should be set to "create".

```javascript
getVisibleJiraProjects(
  cloudId="...",
  action="create"
)
```

--------------------------------

### Get Confluence Page by URL

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Use this function when a Confluence page URL is provided as input.

```javascript
getConfluencePage
```

--------------------------------

### Presenting Task Breakdown to User

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Template for displaying the planned Jira backlog to the user for confirmation before execution.

```text
I've analyzed the spec and here's the backlog I'll create:

**Epic:** [Epic Summary]
[Brief description of epic scope]

**Implementation Tickets (7):**
1. [Story] [Task 1 Summary]
2. [Task] [Task 2 Summary]  
3. [Story] [Task 3 Summary]
4. [Bug] [Task 4 Summary]
5. [Task] [Task 5 Summary]
6. [Story] [Task 6 Summary]
7. [Task] [Task 7 Summary]

Shall I create these tickets in [PROJECT KEY]?
```

--------------------------------

### Parse @Mentions for Action Items

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Use this pattern for explicit assignments starting with '@'. Assignee is text after '@', task is after the action verb.

```text
@john to update documentation
@sarah will create the report  
@mike should review PR #123
@lisa needs to test the feature
```

--------------------------------

### No Results Found Scenario

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Use this response when initial searches yield no relevant information. It prompts the user for clarification and offers alternative search strategies.

```text
I searched across Confluence and Jira but couldn't find information about "[topic]".

This could mean:
- The concept hasn't been documented yet
- It might be called something else (can you provide alternative names?)
- Documentation might be in a different system I don't have access to

Would you like me to:
1. Try searching with different terms?
2. Search for related concepts?
3. Look for mentions in recent Jira tickets?
```

--------------------------------

### Execute Cross-System Search

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Use the search tool to query both Confluence and Jira simultaneously. This is the recommended default approach.

```text
search(
  cloudId="...",
  query="[extracted search terms]"
)
```

```text
search(
  cloudId="...",
  query="Stratus minions"
)
```

--------------------------------

### Get Jira Issue Type Meta With Fields

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Use this function to identify required fields for a specific Jira issue type within a project.

```javascript
getJiraIssueTypeMetaWithFields(
  cloudId="...",
  projectIdOrKey="PROJ",
  issueTypeId="10001"
)
```

--------------------------------

### Request Project Context

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/SKILL.md

Prompt for the user to specify a project when the context is missing.

```text
Which Jira project should I search for similar issues?

Available projects:
- BACKEND (Backend Services)
- MOBILE (Mobile Apps)
- WEB (Web Platform)
- INFRA (Infrastructure)

Or tell me the project key directly (e.g., BACKEND, MOBILE)
```

--------------------------------

### Parse Structured Action Format for Action Items

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Use this for structured formats like 'Action: Name - [task]' or 'AI: Name - [task]'. Assignee is between the prefix and '-', task is after '-'.

```text
Action: John - update documentation
Action Item: Sarah - create the report
AI: Mike - review PR #123
Task: Lisa - test the feature
```

--------------------------------

### Query All Open Issues in a Project

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Use this query to retrieve all issues within a specific project that are not in a 'Done' status. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND status != Done
```

--------------------------------

### Jira JQL for Open Sprints

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/jira-sprint-dashboard-canvas/SKILL.md

Use this JQL when a project or space key is provided but no specific sprint, board, or filter. It targets open sprints within the specified project.

```jql
project = "SPACE_KEY" AND sprint in openSprints() ORDER BY Rank ASC
```

--------------------------------

### Specific vs. Vague Acceptance Criteria

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Illustrates the difference between specific, testable acceptance criteria and vague ones.

```text
✅ API returns 201 status on successful user creation
```

```text
✅ Password must be at least 8 characters and hashed with bcrypt
```

```text
✅ Login form validates email format before submission
```

```text
❌ User can log in
```

```text
❌ It works correctly
```

--------------------------------

### Outdated Information Scenario

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Use this response when documentation is old. It provides the information but warns the user about potential outdatedness and suggests verification.

```text
I found documentation about [topic], but note that it's from [date] and may be outdated.

[Provide the information anyway]

You may want to verify this is still current, especially if it's from more than 
a year ago.
```

--------------------------------

### Get Jira Project Issue Types Metadata

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/spec-to-backlog/SKILL.md

Call `getJiraProjectIssueTypesMetadata` to understand the available issue types within a specific Jira project. This is crucial for identifying 'Epic' and other relevant child issue types.

```javascript
getJiraProjectIssueTypesMetadata(
  cloudId="...",
  projectIdOrKey="PROJ"
)
```

--------------------------------

### Query Issues by Component

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Find all issues within a project that belong to a specific component and are not yet done. Replace 'PROJECT_KEY' and 'ComponentName' accordingly.

```jql
project = "PROJECT_KEY" AND component = "ComponentName" AND status != Done
```

--------------------------------

### Handling Duplicate Action Items

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

This prompt is shown when the same task appears multiple times in the notes, possibly with different formatting. It offers options to combine duplicates, create separate tasks, or skip.

```plaintext
I found what appears to be the same action item twice:
1. "@Sarah to create user stories" (line 15)
2. "Action: Sarah - create user stories" (line 42)

Should I:
1. Create one task (combine duplicates)
2. Create two separate tasks
3. Skip the duplicate

What would you prefer?
```

--------------------------------

### Symptom-Based Search: Loading Issues

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/search-patterns.md

Identify bugs where the user experiences 'infinite loading' or 'stuck loading' issues by searching the summary field. This is useful for UI/UX related problems.

```jql
project = "PROJ" AND (summary ~ "infinite loading" OR summary ~ "stuck loading") AND type = Bug
```

--------------------------------

### JQL: All open issues in project

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/SKILL.md

Use this JQL query to retrieve all issues in a specific project that are not yet completed. It orders results by priority and last updated date.

```jql
project = "PROJECT_KEY" AND status != Done ORDER BY priority DESC, updated DESC
```

--------------------------------

### Search for Java/Backend Exceptions

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/search-patterns.md

Use this pattern to find bugs related to Java or backend exceptions like NullPointerException. Ensure the project and type are correctly specified.

```jql
project = "PROJ" AND text ~ "NullPointerException" AND type = Bug ORDER BY created DESC
```

--------------------------------

### Legacy SSE Endpoint

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/README.md

The legacy Server-Sent Events endpoint is still supported but updating custom clients to point to `/mcp` or `/mcp/authv2` is recommended.

```text
https://mcp.atlassian.com/v1/sse
```

--------------------------------

### Ambiguous Query Scenario

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Present this response when a user's query is vague. It lists related topics found and asks the user to specify their interest.

```text
I found information about several topics related to "[term]":
1. [Topic A] - from Confluence page X
2. [Topic B] - from Jira tickets Y, Z
3. [Topic C] - from documentation W

Which aspect are you most interested in?
```

--------------------------------

### Combined Search: Environment-Specific

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/search-patterns.md

Search for bugs that occurred in a specific environment, such as 'production', and contain 'error keywords'. This is crucial for production issue tracking.

```jql
project = "PROJ" AND text ~ "production" AND text ~ "error keywords" AND type = Bug ORDER BY created DESC
```

--------------------------------

### Jira JQL for Incomplete Work (Snapshot Mode)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/jira-sprint-dashboard-canvas/SKILL.md

Switch to this JQL when open sprint results are empty, stale, or misleading. It captures all work not yet in a 'Done' category, ordered by priority.

```jql
project = "SPACE_KEY" AND statusCategory != Done ORDER BY priority DESC, updated ASC
```

--------------------------------

### Configure Default Atlassian MCP Settings

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/README.md

Update your AGENTS.md file to set default values for Jira project, Confluence space, and Cloud ID. This reduces discovery tool calls and sets maximum search results.

```markdown
## Atlassian Rovo MCP

When connected to atlassian-rovo-mcp:
- **MUST** use Jira project key = YOURPROJ
- **MUST** use Confluence spaceId = "123456"
- **MUST** use cloudId = "https://yoursite.atlassian.net" (do NOT call getAccessibleAtlassianResources)
- **MUST** use `maxResults: 10` or `limit: 10` for ALL Jira JQL and Confluence CQL search operations.
```

--------------------------------

### Query Issues Assigned to a Specific Team Member

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Retrieve all open issues assigned to a particular user. Replace 'PROJECT_KEY' and 'user@example.com' with your project's key and the user's email.

```jql
project = "PROJECT_KEY" AND assignee = "user@example.com" AND status != Done
```

--------------------------------

### Handling Mixed Action Item Formats

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

This prompt appears when some action items have assignees and others do not. It offers options to create all tasks, only assigned tasks, or prompt for assignment.

```plaintext
I found [N] action items:
- [X] with clear assignees
- [Y] without assignees

Should I:
1. Create all [N] tasks ([X] assigned, [Y] unassigned)
2. Only create the [X] tasks with assignees
3. Ask you to assign the [Y] unassigned tasks

Which option would you prefer?
```

--------------------------------

### Symptom-Based Search: Page/Screen Issues

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/search-patterns.md

Find bugs that manifest as user-facing page or screen problems, such as 'blank page' or 'white screen', by searching the summary field.

```jql
project = "PROJ" AND (summary ~ "blank page" OR summary ~ "white screen") AND type = Bug
```

--------------------------------

### Functionality-Based Search: Upload/Download

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/search-patterns.md

Find bugs related to file transfer functionalities by searching for 'upload' or 'download' keywords. This is useful for issues concerning data transfer.

```jql
project = "PROJ" AND (text ~ "upload" OR text ~ "download") AND type = Bug
```

--------------------------------

### Query Unassigned Open Issues

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Find all open issues within a project that have no assignee. This helps in identifying work that needs to be distributed. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND assignee is EMPTY AND status != Done
```

--------------------------------

### Parse Action Items from Structured Action Format

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Parses action items from a structured format like 'Action: Name - Task' or 'AI: Name - Task'.

```plaintext
Action: John - update documentation
Action Item: Sarah - create the report
AI: Mike - review PR #123
```

--------------------------------

### Query Open Issues by Specific Statuses

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Filter open issues by a list of specific statuses. Useful for tracking progress through defined workflow stages. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND status IN ("To Do", "In Progress", "In Review")
```

--------------------------------

### Identify General Statements (Anti-Pattern)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

These are general statements and not action items because they lack a specific assignee.

```text
Documentation needs to be updated
Someone should create a report
The code requires review
```

--------------------------------

### Parse Name + Action Verb for Action Items

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

This pattern identifies action items where a name is followed by an action verb and a task. Assignee is before the verb, task is after.

```text
John to update documentation
Sarah will create the report
Mike should review PR #123
Lisa needs to test the feature
```

--------------------------------

### Parse Action Items from TODO Format

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Parses action items from formats like 'TODO: Task (Assignee)' or '[ ] Assignee: Task'.

```plaintext
TODO: Update documentation (John)
TODO: Create report - Sarah
[ ] Mike: review PR #123
```

--------------------------------

### Query Blocked Issues

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Find all issues that are currently in a 'Blocked' status. This query is essential for identifying impediments. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND status = Blocked
```

--------------------------------

### Parse TODO Format for Action Items

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

This pattern handles TODO-like formats, including those with checkboxes. Assignee is in parentheses or after '-', task is between the marker and assignee.

```text
TODO: Update documentation (John)
TODO: Create report - Sarah
[ ] Review PR #123 (Mike)
- [ ] Test feature - Lisa
```

--------------------------------

### Query Issues Resolved in the Last Week

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Find issues that were marked as 'Done' and resolved within the last 7 days. This helps in reporting on completed work. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND status = Done AND resolved >= -7d
```

--------------------------------

### Format No Duplicates Found

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/SKILL.md

Use this format when no similar issues are found. It summarizes the search criteria, states no duplicates were found, and provides a recommendation to create a new issue.

```markdown
🔍 **Triage Results: No Duplicates Found**

I searched Jira for:
- "Connection timeout" errors
- Mobile login issues
- Authentication failures

No similar open or recent issues found.

**Recommendation:** Create a new bug ticket

**Note:** I found 1 old resolved issue (PROJ-123 from 8 months ago) about login timeouts, but it was for web, not mobile, and was resolved as "configuration error."

Would you like me to create a new bug ticket for this issue?
```

--------------------------------

### Regular Expression Patterns

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/references/action-item-patterns.md

Regex patterns for extracting tasks based on mentions, names, and specific formats.

```regex
@(\w+)\s+(to|will|should)\s+(.+)
```

```regex
([A-Z][\w\s]+?)\s+(to|will|should)\s+(.+)
```

```regex
Action:\s*([A-Z][\w\s]+?)\s*-\s*(.+)
```

```regex
TODO:\s*(.+)\s*\((\w+)\)
```

--------------------------------

### Performance Issue Report Template

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/bug-report-templates.md

Use this template for reporting latency, slow response times, or resource degradation.

```text
[Component]: [Performance Problem] - [Context]
```

```markdown
## Issue Description
[Brief description of the performance problem]

## Performance Metrics
- **Current:** [e.g., 15 second load time]
- **Expected:** [e.g., < 2 seconds]
- **Baseline:** [e.g., Was 1.5s last week]

## Environment
- **Platform:** [Where observed]
- **Environment:** [Production/Staging]
- **Time Observed:** [When it was slow]
- **Load:** [Concurrent users, request rate]

## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. Observe slow response

## Performance Data
```
[Response times, profiling data, slow query logs]
```

## Impact
- **Affected Users:** [e.g., All users during peak hours]
- **Frequency:** [e.g., Consistently slow, Only during peak]
- **Business Impact:** [e.g., Increased bounce rate, User complaints]

## Suspected Cause
[If you have a hypothesis]

## Related Issues
[Any similar past performance issues]

---
*Reported via automated triage*
```

--------------------------------

### Create a New Jira Issue

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/SKILL.md

Creates a new issue in Jira with specified fields and priority.

```text
createJiraIssue(
  cloudId="...",
  projectKey="PROJ",
  issueTypeName="Bug",
  summary="[Clear, specific summary - see below]",
  description="[Detailed description - see below]",
  additional_fields={
    "priority": {"name": "Medium"}  # Adjust based on user input severity assessment
  }
)
```

--------------------------------

### Frontend/UI Issue Report Template

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/bug-report-templates.md

Use this template for reporting visual bugs, UI crashes, or browser-specific issues.

```text
[Platform] [Component]: [Symptom]
```

```markdown
## Issue Description
[Brief description of the visible problem]

## Environment
- **Platform:** [iOS/Android/Web]
- **Version:** [App/Browser version]
- **OS:** [e.g., iOS 16.5, Windows 11, macOS 13]
- **Device:** [e.g., iPhone 14 Pro, Chrome on Desktop]

## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Visual Evidence
[Screenshots or screen recording if available]

## User Impact
- **Frequency:** [e.g., Every time, Intermittent]
- **Affected Users:** [e.g., All iOS users, Only Safari users]
- **Severity:** [e.g., Cannot complete checkout, Minor visual glitch]

## Console Errors
```
[Browser console errors if applicable]
```

## Additional Context
[Network conditions, user permissions, etc.]

## Related Issues
[Any similar past issues]

---
*Reported via automated triage*
```

--------------------------------

### Query High Priority Open Issues

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/generate-status-report/references/jql-patterns.md

Retrieve open issues that are marked with 'Highest' or 'High' priority. This helps in identifying critical tasks. Replace 'PROJECT_KEY' with your project's key.

```jql
project = "PROJECT_KEY" AND status != Done AND priority IN ("Highest", "High")
```

--------------------------------

### Jira JQL for Unowned Unfinished Work (Follow-up)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/jira-sprint-dashboard-canvas/SKILL.md

Finds unfinished work items that are not assigned to anyone, ordered by priority. Helps identify tasks that may be falling through the cracks.

```jql
<scope> AND statusCategory != Done AND assignee is EMPTY ORDER BY priority DESC, updated ASC
```

--------------------------------

### Jira JQL for Recently Updated Work (Snapshot Mode)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/jira-sprint-dashboard-canvas/SKILL.md

Use this JQL to capture work updated within the last 60 days, ordered by update time. This is a default window unless a different period is specified.

```jql
project = "SPACE_KEY" AND updated >= -60d ORDER BY updated DESC
```

--------------------------------

### Handling Long Task Descriptions

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

This prompt appears if an action item's description exceeds 200 characters. It offers options to use the first sentence as a summary, the full text as a summary, or allow user editing for conciseness.

```plaintext
The task "[long text...]" is quite detailed.

Should I:
1. Use first sentence as summary, rest in description
2. Use full text as summary
3. Let you edit it to be more concise

Which would you prefer?
```

--------------------------------

### Execute Targeted Jira Search

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Use JQL to search specifically within Jira when looking for tickets, bugs, or historical implementation details.

```text
searchJiraIssuesUsingJql(
  cloudId="...",
  jql="text ~ 'search terms' OR summary ~ 'search terms'"
)
```

```text
text ~ "Stratus minions"
summary ~ "authentication" AND type = Bug
text ~ "deployment" AND created >= -90d
```

--------------------------------

### Create Jira Issue

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/capture-tasks-from-meeting-notes/SKILL.md

Function to create a new Jira issue. Requires project key, issue type name, summary, description, and assignee account ID.

```javascript
createJiraIssue(
  cloudId="...",
  projectKey="PROJ",
  issueTypeName="[Task or available type]",
  summary="[Task description]",
  description="[Full description with context]",
  assignee_account_id="[looked up account ID]"
)
```

--------------------------------

### Jira JQL for Blocked Work Items (Follow-up)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/jira-sprint-dashboard-canvas/SKILL.md

Identifies work items that are explicitly blocked by status, contain 'blocked' in their text, or are labeled as 'blocked' or 'blocker'. Ordered by priority.

```jql
<scope> AND statusCategory != Done AND (status = Blocked OR text ~ "blocked" OR labels in (blocked, blocker)) ORDER BY priority DESC, updated ASC
```

--------------------------------

### Jira JQL for High-Priority Unfinished Work (Follow-up)

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/jira-sprint-dashboard-canvas/SKILL.md

Retrieves unfinished work items with the highest or high priority, ordered by priority. Useful for focusing on critical tasks.

```jql
<scope> AND statusCategory != Done AND priority in (Highest, High) ORDER BY priority DESC, updated ASC
```

--------------------------------

### Restricted/Private Content Scenario

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/search-company-knowledge/SKILL.md

Inform the user when search results include inaccessible content. List the locations and mention potential permission issues.

```text
Search results mention [topic] in the following locations, but I don't have 
access to view the full content:
- Confluence page: [title] (Space: [SPACE])
- Jira issue: PROJ-123

You may need to access these directly or check your permissions.
```

--------------------------------

### Multi-Angle Strategy: Symptom-Based

Source: https://github.com/atlassian/atlassian-mcp-server/blob/main/skills/triage-issue/references/search-patterns.md

The third step in the strategy, this JQL pattern uses a broad search based on user-reported symptoms in the summary field.

```jql
project = "PROJ" AND summary ~ "user symptom" AND type = Bug ORDER BY priority DESC
```