'jira' 검색 결과

Manage organization-wide Atlassian administration, including user onboarding and removal, group permissions, sign-in settings, and app integrations. It provides workflows for access reviews, configuration changes, operational checks, and recovery planning, primarily through admin consoles and REST APIs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Onboarding employees and removing access for departing staff
• Reviewing Jira and Confluence permissions
• Planning single sign-on and external integrations

JIRA issue CRUD via jira-as. NOT lifecycle (mk:jira-lifecycle), comments (mk:jira-collaborate), bulk (mk:jira-bulk), links (mk:jira-relationships), or time/sprint (mk:jira-time/agile).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기존 프로젝트의 구현 방식에 맞춰 외부 API 연동을 추가합니다. 설정, 인증, 오류 처리부터 등록과 테스트까지 기존 코드와 일관되게 구성합니다.

• 기존 프로젝트에 Jira 연동 추가
• 기존 방식에 맞는 Slack 연동 구현
• 연동 등록과 테스트 정비

Organize Confluence documentation with clear page hierarchies, reusable templates, and access plans. Create and update pages, embed Jira reports, and audit existing content to identify outdated material and establish review responsibilities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restructure a team's Confluence space
• Standardize meeting notes and decision logs
• Embed Jira issues and charts in documentation

Bulk JIRA operations on 10+ issues via the jira-as wrapper: bulk transition / assign / set-priority / clone / delete. Dry-run is MANDATORY first. Triggers: 'bulk update N issues', 'mass transition', 'transition 50+ issues to Done', 'bulk-clone', 'bulk-delete'. NOT for single-issue ops (mk:jira-issue / mk:jira-lifecycle).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate Jira ticket complexity + inconsistencies via the jira-evaluator agent. Read-only. Triggers: 'evaluate KEY', 'analyze ticket complexity for KEY', 'check ticket quality for KEY'. NOT for estimation (mk:jira-estimator); NOT for full RCA (mk:jira-analyst).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Heuristic story-point estimation for a single Jira ticket via the jira-estimator agent. Read-only. Triggers: 'estimate KEY', 'story points for KEY', 'how complex is KEY'. NOT for complexity-only analysis (mk:jira-evaluator); NOT for full RCA (mk:jira-analyst).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: 'branch name for KEY', 'PR description for KEY', 'parse commits for issue keys', 'link PR to KEY'. NOT for executing git/gh commands directly (mk:ship); NOT for issue CRUD (mk:jira-issue).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organize Linear or Jira backlogs through the Composio CLI, a command-line tool. Fetch issues in bulk, group likely duplicates, update labels, priorities, and owners, then share a summary of changes in Slack.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Weekly reviews of unassigned or stale issues
• Post-release bug reviews and owner assignment
• Grouping duplicate reports and linking related issues

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that can be worked on and tracked in Jira. Requires a configured Atlassian MCP server. Does not produce the work-items file itself — use plan-work-items to break a plan into work items first. Does not post to GitHub — use work-items-to-issues for GitHub issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Routing skill — recommends the correct mk:jira-* leaf for any Jira task. Triggers: 'jira', 'jira ticket', ambiguous Jira intent. NOT an executor — every actual operation forks via a leaf skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JIRA custom field discovery + configuration via the jira-as wrapper. Triggers: 'field ID for X', 'list custom fields', 'check fields for project PROJ', 'configure agile fields for board'. Read ops are open; create/configure-agile require admin. NOT for setting per-issue field values (mk:jira-issue update).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create separate Git working directories for issue fixes, pull request reviews, and feature development. Optional tmux terminal sessions help manage parallel tasks, return to ongoing work, and clean up completed sessions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Working on several issue fixes in parallel
• Preparing a separate workspace for a pull request review
• Returning to an ongoing development session

Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create issues from validated security findings
• Find and reuse existing issues for the same finding
• Register a reviewed batch of security issues

Jira expert for project setup, workflow design, JQL queries, custom fields, automation rules, dashboards, and reporting. Use for Jira configuration, advanced search, board and dashboard creation, and technical Jira operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JIRA project/user/group/scheme/automation admin via jira-as. Requires admin role; destructive ops need 2-step confirm. NOT per-issue ops (mk:jira-issue/lifecycle) or JSM admin (mk:jira-jsm).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JIRA comments, attachments, watchers, notify via jira-as. Internal-vs-public comment safety enforced. NOT issue CRUD (mk:jira-issue) or issue links (mk:jira-relationships).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive JIRA workflow lifecycle via jira-as: transition, assign, resolve, reopen, versions, components. NOT issue CRUD (mk:jira-issue) or bulk transitions (mk:jira-bulk).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JIRA search + filter management via jira-as; JQL injection-safe. NOT single-issue CRUD (mk:jira-issue) or bulk writes (mk:jira-bulk).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bulk JIRA ops (10+ issues): transition/assign/priority/clone/delete via jira-as; dry-run mandatory. NOT single-issue ops (mk:jira-issue, mk:jira-lifecycle).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JIRA Service Management via jira-as: service desks, requests, customers, orgs, queues, SLAs, approvals. Requires JSM tenant + agent role. NOT core issue ops (mk:jira-issue) or admin (mk:jira-admin).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.