xxiaoxiong/dsh-issue-tracker
dsh-issue-tracker
已收录
1
Tools
Bundle 已验证
功能介绍
Jira Cloud 工单集成,提供 8 个模型工具用于工单查询、项目与流转查询、创建、更新、评论和状态流转;写操作默认关闭并支持 dry-run。
适合
- 需要直接通过 DeepSeek Harness 管理 Jira Cloud 工单的团队。
- 以工单搜索、项目查询和可用流转查询为主的只读工作流。
- 需要通过显式开启写权限和 dry-run 来控制 Jira 创建、更新、评论及状态流转的流程。
不适合
- Jira Cloud REST API v3 之外的工单系统。
- 缺少 Jira 地址及受支持 API 凭据或 bearer 凭据的环境。
- 无法显式开启写权限或采用 dry-run 防护的无人值守写入自动化。
- 不符合 Node.js `^22.19.0 || >=24.0.0` 或文档所述 Harness 版本的运行环境。
README
dsh-issue-tracker
Jira Cloud issue-tracker service and model-facing tools for DeepSeek Harness.
The package is one installable DSH bundle with three internal roles:
- a provider-neutral Cordis
issueTrackerservice; - a Jira Cloud REST API v3 provider;
- eight tools registered through the public DSH
ToolRuntimeservice.
The plugin is read-only by default. Create, update, comment, and transition
operations require an explicit writeEnabled: true; every write tool also
supports a side-effect-free dryRun.
Requirements
- Node.js
^22.19.0 || >=24.0.0 - DeepSeek Harness
0.1.0-rc.6 - Jira Cloud REST API v3
Install
dsh plugin --profile web add dsh-issue-tracker
The bundle row stays disabled until these variables are available:
$env:JIRA_BASE_URL = 'https://your-domain.atlassian.net'
$env:JIRA_EMAIL = 'you@example.com'
$env:JIRA_API_TOKEN = 'your-api-token'
Writes remain disabled. Enable them only when intended:
$env:DSH_ISSUE_TRACKER_WRITE_ENABLED = 'true'
Restart DSH, then inspect the composed row:
dsh --profile web --dump-config
For OAuth bearer authentication or non-environment configuration, replace the
issue-tracker row in the profile’s cordis.patch.yml; a patch replaces the
whole row, so restate every field:
- id: issue-tracker
name: dsh-issue-tracker
config:
baseUrl: https://your-domain.atlassian.net
auth:
type: bearer
accessToken: !!js process.env.JIRA_ACCESS_TOKEN
writeEnabled: false
Tools
| Tool | Purpose | Writes |
|---|---|---|
issue_get |
Read one issue | No |
issue_search |
Search with filters or raw JQL | No |
issue_transitions |
List available transitions | No |
issue_projects |
List visible projects | No |
issue_create |
Create an issue | Yes |
issue_update |
Update issue fields | Yes |
issue_comment |
Add a comment | Yes |
issue_transition |
Apply a transition | Yes |
All HTTP calls honor the DSH tool cancellation signal and a configured request
deadline. Structured filters are JQL-escaped; providerQuery is intentionally
raw JQL and should be governed like any other privileged query input.
Security
- HTTPS is required unless
allowInsecureHttp: trueis explicitly set. - Credentials in
baseUrlare rejected. - Secrets are marked with Schemastery’s secret role.
- The plugin does not log credentials, prompts, issue bodies, or comments.
- No telemetry is collected or sent by this package.
See docs/security.md for the complete boundary.
Uninstall
dsh plugin --profile web remove dsh-issue-tracker
Cordis owns both the service registration and tool registrations, so unloading
the bundle removes all eight tools and the issueTracker service.
Verification status
The release is typechecked and tested on Windows with real Cordis and DSH
0.1.0-rc.6 packages. HTTP behavior is tested with mocked Jira responses; no
live Jira tenant or production credential was used. See
docs/verification-report.md.
中文说明
这是一个面向 DeepSeek Harness 的 Jira Cloud 工单插件。安装一个 npm 包即可
获得通用 issueTracker 服务和 8 个模型工具。插件默认只读;所有写操作必须显式
开启 writeEnabled,并且可以先用 dryRun 验证参数而不产生副作用。
许可证:MIT。
常见问题常见问题
在启用了 DSH 的终端中执行已验证命令 dsh plugin --profile default add github:xxiaoxiong/dsh-issue-tracker。命令会解析公开 package 元数据,并保持插件与本页展示的目录身份一致。
兼容性以页面上展示的 bundle 与 profile 状态为准。如果某个 profile 尚未检测到,请先保持禁用,并在生产启用前阅读仓库文档。
GitHub 链接和 activity 元数据是 release 与维护状态的来源。新版本发布后重新查看本页,确认目录已经观察到最新版本。