← 插件

Jira Sprint Workspace

Turn your assigned Jira sprint issues into Paseo workspaces. Browse your board, read issue details, and start an agent on an issue without leaving Paseo.

$ paseo plugin add mbranicky/jira-dashboard
报告问题
Jira Sprint Workspace 截图 1Jira Sprint Workspace 截图 2Jira Sprint Workspace 截图 3Jira Sprint Workspace 截图 4Jira Sprint Workspace 截图 5Jira Sprint Workspace 截图 6Jira Sprint Workspace 截图 7

该插件的概览尚未翻译为你的语言,因此以英文显示。

See your assigned Jira Cloud sprint issues in the board's own columns. Search cards, follow the active sprint or choose an active/future sprint, and turn issues into Paseo workspaces with dedicated agents.

Configure a Jira Cloud board URL, then save additional boards on the same site. Connect with Atlassian MCP OAuth, a Teamwork Graph CLI OAuth profile on the host, or a private host-side jira.env file containing JIRA_EMAIL and JIRA_API_TOKEN. MCP uses explicit host-browser sign-in and protected host storage; see the MCP guide. MCP resolves workflow destinations through exact status lookup; ambiguous matches require Jira. MCP and Teamwork Graph writes are off by default; enable Allow Jira changes for moves, comments and uploads. See the Teamwork Graph guide for OAuth setup and CLI limitations. Test connection checks dashboard reads before saving. Requires Paseo 0.14.x, 0.15.x or 0.16.x, its CLI and npm on the daemon's PATH, and Git for worktree isolation. The verified Paseo host is macOS on Apple silicon. Linux has automated test coverage on Ubuntu. Windows and Intel Mac hosts are unverified. See the Jira setup guide for scopes and file permissions.

Map Jira project keys to existing Paseo projects. Select a provider and isolation mode; optionally override model and agent mode. Play creates or reuses an issue-named workspace and agent without changing Jira status. An existing active workspace gets an Open workspace action. Existing issue branches/worktrees are reused; multiple matches open a choice dialog. New branches use the project's checked-out branch. Project-directory isolation shares files with other work in that project.

Optionally configure an entry skill. The initial prompt is /<skill> <issue-key>, for example /init-issue DEMO-1234; leaving the skill blank opens an agent without sending a prompt. You supply the skill and its Jira connectivity. The prompt goes to the selected agent provider; subsequent skill/tool activity may send Jira content or repository data to that provider according to your configuration. Uncertain prompt delivery is not automatically retried. Workspaces receive In Progress and, for recognized types, Story or Bug labels.

Drag issues between dashboard columns to request a Jira workflow transition. Same-column drops do nothing. Jira determines allowed transitions; supported required fields are collected in a dialog, and rejected moves keep the original column. A mapping can start or reuse work after a successful move into its selected column. Moving an issue directly in Jira never launches an agent.

Open rich issue details in a modal or a resizable, collapsible dashboard panel; narrow screens use full-screen details. Workspace Jira tabs detect the relevant issue from plugin associations or workspace/agent names. Description, attachments and comments collapse independently. Read and post comments with Markdown input and preview. Replies are top-level comments linked to the original; the dashboard nests recognized linked replies as well as native parent relationships supplied by Jira. View/download attachments, preview images and explicitly upload files. Local desktop image previews can open in the browser; remote/mobile clients use in-app previews. MCP uploads have been tested only with simulated responses. If confirmation fails, refresh the attachments and check Jira before retrying. See the setup guide for transfer limits.

Credentials stay on the daemon and are sent to Atlassian for authentication, never to agents by the plugin. Authorized Paseo clients on that host share the configured account's Jira view. Jira data travels between Atlassian, the daemon and connected clients; comments, uploads and workflow moves write to Jira only through their explicit actions. Workspace associations persist on the host. Panel state is session-only. Comment drafts use device-local app/browser storage, with an explicit session-only fallback when unavailable. Failed writes are not automatically retried.

Direct token entry, in-plugin Paseo project creation, native threaded reply posting and explicit skill rerun controls are not available. The connection test does not verify comment, attachment or transition permissions. Unsupported workflow fields must be completed in Jira.

Unsent comments and linked replies are saved in this device's local app/browser storage, scoped to the host, Jira site, verified account and issue. Drafts survive plugin reloads on desktop and browser clients. Where durable storage is unavailable, including native mobile clients, the editor clearly reports session-only retention. Drafts are never submitted automatically; uncertain delivery remains protected after reopening. Save named boards from the connected Jira site and switch between them from the board header. Each board remembers its sprint and session search. Board selection is shared by clients on the host; switching preserves the existing connection method, credentials and project mappings. On desktop, focus a board control and use J/K to move through visible issues, / to focus search, and Enter to open the focused issue. Shortcuts leave text editors, dialogs and the sprint menu alone. Issue details and workspace panels show linked issues and subtasks with Jira's relationship labels, status and links back to Jira. When the connection omits relationship fields, the panel explains that the list is incomplete. Filter the loaded sprint by labels, priority, issue type, parent or fix version. Combine filters with key/title search and save named views for each board. Saved views are shared with other clients connected to the same Paseo host.

Workspace buttons show agent activity at a glance, including approval, running, review and done states, while still opening the workspace. Activity refreshes every 15 seconds while visible and is separate from Jira status. When moving an issue has several possible Jira transitions, clear choices appear above the board for review before confirmation.