pipe-kan 0.25.4 → 0.27.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -12,12 +12,14 @@ npx pipe-kan
12
12
 
13
13
  Opens `http://127.0.0.1:5173`. No clone, no `bun install`. `bunx` / `npx` installs the published package into a cache and runs it.
14
14
 
15
- First paint is the Fixture. If `jira` is on PATH, the process then Refresh-es from your existing `jira init`. If not, Refresh and Move use the in-process store.
15
+ First paint is the Fixture. If `jira` is on PATH, the process then Refresh-es from your existing `jira init`. If not, Refresh, Move, Create, and Edit use the in-process store.
16
16
 
17
17
  The published CLI is on npm. From a clone: `bun run build && bun dist/pipe-kan.js`.
18
18
 
19
19
  - Left: All stories and All epics. Center: Cards (one Column per status in the payload). Right: Open URL; remote Jira is a link, not an iframe.
20
20
  - Drop a Card on a Column to Move (`jira issue move`).
21
+ - Column `+` or Cmd+K **Create issue** opens a composer. **Create with AI** seeds the Agent to draft and call `create_issue` after approval.
22
+ - Double-click a Card or Open-pane **Edit** to change summary, description, and labels (`jira issue edit`).
21
23
  - Drag a Column to change status order. The order is stored locally and kept after Refresh.
22
24
  - Same-Column drop does not write back to Jira.
23
25
  - Collapse the left pane to hide Epics; the Board header expands it again.
@@ -64,7 +66,7 @@ Pipe is the first Board. Refresh and Move still go through `jira` when it is on
64
66
 
65
67
  ## Limits
66
68
 
67
- - Write-back is `jira issue move` only. Intra-column rank is not persisted.
69
+ - Write-back is `jira issue move`, `jira issue create`, and `jira issue edit`. Intra-column rank is not persisted.
68
70
  - Never a direct Jira REST Write-back.
69
71
  - Work Jira needs `jira` on PATH and a token. This repo does not ship one.
70
72