SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsjira-markdown-conversion

jira-markdown-conversion

Agents & models

View repository

Updated 10-15 17:33

About this skill

Jira to Markdown Conversion Skill

Use Atlassian MCP to retrieve Jira data and convert it into highly AI-readable Markdown format.

Supported Tasks

  • Convert detailed information of a Jira issue into a Markdown document
  • Convert a Jira backlog (list of unresolved issues) into a Markdown table
  • Document the contents of a Sprint in Markdown format
  • Convert multiple issues into a structured Markdown report

Environment Information

Cloud ID

  • hadron.atlassian.net: f6e0f50a-4acf-4011-90fa-8fcc9b50cd86

Available MCP Tools

  • mcp__atlassian__getJiraIssue - Retrieve individual issue details
  • mcp__atlassian__searchJiraIssuesUsingJql - JQL search
  • mcp__atlassian__getVisibleJiraProjects - Retrieve project list

Markdown Conversion Patterns

1. Converting Issue Details to Markdown

# [ISSUE-KEY] タイトル

## メタデータ
- **ステータス**: {status}
- **タイプ**: {issueType}
- **担当者**: {assignee or [未割り当て]}
- **優先度**: {priority or [未設定]}
- **作成日**: {created}
- **更新日**: {updated}

## 説明
{description or [未記入]}

## コメント
{comments}

## 添付ファイル
{attachments}

2. Converting Backlog to a Table

## バックログ一覧

| キー | タイプ | サマリー | ステータス | 担当者 | 優先度 | 作成日 |
|------|--------|----------|------------|--------|--------|---------|
| SCRUM-1 | Feature | タスク 1 | Idea | [未割り当て] | [未設定] | 2026-01-06 |
| SCRUM-2 | タスク | タスク 2 | To Do | [未割り当て] | [未設定] | 2026-01-06 |

3. Converting Sprint Information to Markdown

## Sprint情報

- **名前**: SCRUM Sprint 0
- **状態**: active
- **開始日**: 2026-01-06
- **終了日**: 2026-01-20

### Sprint内のIssue

| キー | サマリー | ステータス | 担当者 |
|------|----------|------------|--------|
| ... | ... | ... | ... |

Data Retrieval Workflow

Backlog Retrieval

  1. mcp__atlassian__searchJiraIssuesUsingJqlUse
  2. JQL: project = {PROJECT_KEY} AND resolution = Unresolved ORDER BY created DESC
  3. Fields to retrieve: summary, status, issuetype, priority, created, assignee

Individual Issue Retrieval

  1. mcp__atlassian__getJiraIssueUse
  2. issueIdOrKey: {ISSUE_KEY}
  3. Retrieve all fields

Structuring Rules

  1. Place metadata at the beginning - Display important information first
  2. Explicit indication of blank items - [未記入]、[未割り当て]、[未設定]and state clearly
  3. Date formatting - Convert from ISO format to a readable format (YYYY-MM-DD)
  4. Distinguish between placeholders and actual data - Clearly separate actual data from explanatory text
  5. Maintain hierarchical structure - Express the importance of information through heading levels
  6. Use of tables - Always represent list data in table format

Precautions During Conversion

  • For null values,[未設定]or[未記入]and display
  • If Japanese and English field names are mixed, prioritize Japanese
  • The Sprint field is retrieved as customField_10020
  • Issue keys must always be linked or highlighted

Usage Examples

Example 1: Retrieving a project backlog

「SCRUMプロジェクトのバックログをMarkdownで出力して」
→ JQL検索 + Markdown変換

Example 2: Individual issue details

「SCRUM-5の詳細をMarkdownで」
→ Issue取得 + Markdown変換

Example 3: Visualizing Sprint contents

「Sprint 0の内容をまとめて」
→ Sprint検索 + Issue一覧取得 + Markdown変換

References

  • Atlassian MCP Server Documentation
  • Jira REST API Reference
  • JQL (Jira Query Language) Syntax