jira by membranedev/application-skills
npx skills add https://github.com/membranedev/application-skills --skill jiraJira 是一款用于软件开发团队的项目管理和问题跟踪工具。它允许团队规划、跟踪和发布软件,同时管理缺陷和其他问题。
官方文档:https://developer.atlassian.com/cloud/jira/platform/
此技能使用 Membrane CLI 与 Jira 交互。Membrane 会自动处理身份验证和凭据刷新——因此您可以专注于集成逻辑,而无需处理身份验证的底层细节。
安装 Membrane CLI,以便您可以从终端运行 membrane 命令:
npm install -g @membranehq/cli
membrane login --tenant
浏览器窗口将打开以进行身份验证。
无头环境: 运行该命令,复制打印出的 URL 供用户在浏览器中打开,然后使用 membrane login complete <code> 完成验证。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
创建新连接:
membrane search jira --elementType=connector --json
从 output.items[0].element?.id 获取连接器 ID,然后:
membrane connect --connectorId=CONNECTOR_ID --json
用户在浏览器中完成身份验证。输出结果包含新的连接 ID。
当您不确定连接是否已存在时:
检查现有连接:
membrane connection list --json
如果存在 Jira 连接,请记下其 connectionId。
当您知道要做什么但不知道确切的 action ID 时:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
这将返回包含 id 和 inputSchema 的操作对象,以便您知道如何运行它。
| 名称 | 键 | 描述 |
|---|---|---|
| 获取当前用户 | get-current-user | 获取当前已验证用户的详细信息 |
| 获取状态 | get-statuses | 获取所有问题状态 |
| 获取优先级 | get-priorities | 获取所有问题优先级 |
| 获取问题类型 | get-issue-types | 获取用户可用的所有问题类型 |
| 获取用户 | get-user | 根据账户 ID 获取特定用户的详细信息 |
| 搜索用户 | search-users | 根据姓名、电子邮件或账户 ID 搜索用户 |
| 获取项目 | get-project | 获取特定项目的详细信息 |
| 获取所有项目 | get-all-projects | 获取用户可见的所有项目列表 |
| 删除评论 | delete-comment | 从问题中删除评论 |
| 更新评论 | update-comment | 更新问题上的现有评论 |
| 获取评论 | get-comments | 获取问题的所有评论 |
| 添加评论 | add-comment | 向问题添加评论 |
| 分配问题 | assign-issue | 将问题分配给用户 |
| 转换问题状态 | transition-issue | 使用工作流转换将问题转换到新状态 |
| 获取问题转换 | get-issue-transitions | 获取问题的可用工作流转换 |
| 搜索问题 (JQL) | search-issues-jql | 使用 JQL (Jira 查询语言) 搜索问题 |
| 删除问题 | delete-issue | 从 Jira 中删除问题 |
| 更新问题 | update-issue | 更新 Jira 中的现有问题 |
| 获取问题 | get-issue | 根据 ID 或键获取特定问题的详细信息 |
| 创建问题 | create-issue | 在 Jira 中创建新问题 |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
传递 JSON 参数:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
当可用操作无法满足您的用例时,您可以通过 Membrane 的代理直接向 Jira API 发送请求。Membrane 会自动将您提供的路径附加到基础 URL,并注入正确的身份验证标头——如果凭据过期,还会透明地刷新凭据。
membrane request CONNECTION_ID /path/to/endpoint
常用选项:
| 标志 | 描述 |
|---|---|
-X, --method | HTTP 方法 (GET, POST, PUT, PATCH, DELETE)。默认为 GET |
-H, --header | 添加请求头(可重复),例如 -H "Accept: application/json" |
-d, --data | 请求体(字符串) |
--json | 发送 JSON 正文并设置 Content-Type: application/json 的简写 |
--rawData | 按原样发送正文,不做任何处理 |
--query | 查询字符串参数(可重复),例如 --query "limit=10" |
--pathParam | 路径参数(可重复),例如 --pathParam "id=123" |
membrane action list --intent=QUERY(将 QUERY 替换为您的意图)以查找现有操作。预构建的操作处理了原始 API 调用可能遗漏的分页、字段映射和边界情况。每周安装次数
141
代码仓库
GitHub 星标数
18
首次出现
13 天前
安全审计
已安装于
openclaw141
gemini-cli141
claude-code141
github-copilot141
codex141
kimi-cli141
Jira is a project management and issue tracking tool used by software development teams. It allows teams to plan, track, and release software, as well as manage bugs and other issues.
Official docs: https://developer.atlassian.com/cloud/jira/platform/
This skill uses the Membrane CLI to interact with Jira. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
Create a new connection:
membrane search jira --elementType=connector --json
Take the connector ID from output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
The user completes authentication in the browser. The output contains the new connection id.
When you are not sure if connection already exists:
Check existing connections:
membrane connection list --json
If a Jira connection exists, note its connectionId
When you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| Get Current User | get-current-user | Get details of the currently authenticated user |
| Get Statuses | get-statuses | Get all issue statuses |
| Get Priorities | get-priorities | Get all issue priorities |
| Get Issue Types | get-issue-types | Get all issue types available to the user |
| Get User | get-user | Get details of a specific user by account ID |
| Search Users | search-users | Search for users by name, email, or account ID |
| Get Project | get-project | Get details of a specific project |
| Get All Projects | get-all-projects | Get a list of all projects visible to the user |
| Delete Comment | delete-comment |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the Jira API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.Weekly Installs
141
Repository
GitHub Stars
18
First Seen
13 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
openclaw141
gemini-cli141
claude-code141
github-copilot141
codex141
kimi-cli141
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
44,900 周安装
| Delete a comment from an issue |
| Update Comment | update-comment | Update an existing comment on an issue |
| Get Comments | get-comments | Get all comments on an issue |
| Add Comment | add-comment | Add a comment to an issue |
| Assign Issue | assign-issue | Assign an issue to a user |
| Transition Issue | transition-issue | Transition an issue to a new status using a workflow transition |
| Get Issue Transitions | get-issue-transitions | Get available workflow transitions for an issue |
| Search Issues (JQL) | search-issues-jql | Search for issues using JQL (Jira Query Language) |
| Delete Issue | delete-issue | Delete an issue from Jira |
| Update Issue | update-issue | Update an existing issue in Jira |
| Get Issue | get-issue | Get details of a specific issue by its ID or key |
| Create Issue | create-issue | Create a new issue in Jira |
| Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |