atlass 2.0.0 → 2.2.0

package/README.md

@@ -72,9 +72,10 @@ Writes `PROJ-123.md` or `123456-title-slug.md` to the current directory, with
 attachments in a sibling `<name>.assets/` folder. Pass `--out` with a directory
 or file path to write elsewhere. Existing files are overwritten.
 
-Each file has YAML frontmatter, an H1, the body as Markdown, a `## Comments`
-section, and an `## Attachments` section. Inline images link to the local copy
-when they can be matched to an attachment.
+Each file has YAML frontmatter, an H1, the body as Markdown, then a
+`<!-- atlass:generated -->` line followed by the `## Comments` and
+`## Attachments` sections. Inline images link to the local copy when they can be
+matched to an attachment.
 
 ## Update
 
@@ -88,8 +89,13 @@ atlass confluence update file.md --title      # also push the H1 as the title
 atlass confluence update file.md -m "fix typo"
 ```
 
-Both accept `--dry-run` to preview and `--force` to skip the checks below. The
-body sent is everything between the H1 and `## Comments`.
+Both accept `--dry-run` to preview and `--force` to skip the checks below. A
+Confluence dry run also prints a diff of the body against the server. A dry run
+exits 1 when the real update would refuse, or would need to ask and cannot
+because there is no terminal or `--no-input` is set.
+
+The body sent is everything between the H1 and the `<!-- atlass:generated -->`
+line, or the first `## Comments` or `## Attachments` in older copies.
 
 - The update aborts if the issue or page changed on the server since the copy.
 - Panels, macros, expands, and layouts were flattened on copy and cannot be
@@ -97,6 +103,9 @@ body sent is everything between the H1 and `## Comments`.
   overwriting.
 - Confluence uploads local images referenced in the body as attachments. Jira
   update does not support image changes yet.
+- After an update, the new `updated` (and for Confluence, `version`, and `title`
+  with `--title`) is written back to the frontmatter, so the file can be pushed
+  again without a fresh copy.
 
 ## Create
 
@@ -123,6 +132,18 @@ assignees take `me`, an account id, or a name matching one assignable user.
 `--dry-run` prints the resolved payload. `--json` prints the created key, id,
 and URL. `jira fields` shows what each field expects.
 
+```bash
+atlass confluence create notes.md --space DEV
+atlass confluence create notes.md --space DEV --parent 123456 --star
+```
+
+`confluence create` publishes a Markdown file as a new page. The title is the
+H1, or `title` in the frontmatter. The space comes from `--space` or `space` in
+the frontmatter, and the page goes under the space homepage unless `--parent`
+names another page. Local images are uploaded as attachments. The file then gets
+the same frontmatter as a copy, so `update` works on it straight away.
+`--dry-run` previews and exits 1 if the create would be refused.
+
 ## List
 
 ```bash
@@ -136,9 +157,12 @@ atlass confluence list --space DOCS
 `jira list` shows issues assigned to you as `KEY  Status  Age  Summary`, with
 In Progress first, then To Do, and the most recently updated at the top of each
 group. Done issues are left out; `--all` adds those updated in the last 30 days.
+`--limit` keeps the first rows of that order; without it, all are shown.
 
 `confluence list` shows the pages you starred as `ID  SPACE  Age  Title`, most
-recently updated first. `--limit` works as for search.
+recently updated first. `--limit` works as for search. Star or unstar a page
+with `atlass confluence star <page>` or `unstar <page>`, where `<page>` is an
+id, a URL, or a copied `.md` file.
 
 For both, `--json` and `--copy` work as for search.
 
@@ -152,10 +176,12 @@ atlass confluence search "onboarding" --space DOCS --label runbook
 ```
 
 Jira filters on `--project`, `--assignee`, `--reporter`, `--status`, `--type`,
-`--label`, `--updated` and `--open`; Confluence on `--space`, `--label`,
-`--updated` and `--starred`. Repeating a flag matches any of its values;
-different flags must all match. `--assignee` and `--reporter` take `me`, an
-account id, or a name to look up. `--updated` takes `7d`, `2w`, `3m` or
+`--label`, `--sprint`, `--updated` and `--open`; Confluence on `--space`,
+`--label`, `--updated` and `--starred`. Repeating a flag matches any of its
+values; different flags must all match. `--assignee` and `--reporter` take `me`,
+an account id, or a name to look up. `--sprint` takes `active`, `future`, a
+sprint id, or a sprint name; names can repeat across boards, an id cannot.
+`--updated` takes `7d`, `2w`, `3m` or
 `YYYY-MM-DD`. Results sort by most recently updated and use the same columns
 as `jira list` and `confluence list`.
 
@@ -170,6 +196,19 @@ atlass confluence cql "label = runbook AND creator = currentUser()"
 to pick results interactively and copy each one, with `--out` as the target
 directory. All four work on both search commands.
 
+`--field` adds a field's value to each issue on `jira search`, `jira jql` and
+`jira list`:
+
+```bash
+atlass jira search --assignee me --status Closed --field "Story Points" --json
+```
+
+It takes a field id or a name, ignoring case, and repeats for more fields. A
+name several fields share fails and lists their ids; `atlass jira fields
+--search` finds the one you want. Each field becomes a column after the status.
+With `--json`, each issue gains a `fields` object of raw values keyed by the
+name you passed.
+
 Discovery aids for the filters:
 
 ```bash
@@ -177,6 +216,42 @@ atlass jira projects [query]
 atlass jira statuses [query] [--project PROJ]
 ```
 
+## Boards
+
+```bash
+atlass jira boards [query] [--project PROJ]
+atlass jira board <id|url|name> [--json]
+```
+
+`boards` lists every board as `ID  Type  Name  Project`, filtered by name and
+project key. Boards that span projects leave the project cell empty.
+
+`board` shows one board: the field it estimates with, its filter JQL, and each
+column's statuses with their categories. A name must match exactly, ignoring
+case; if several boards share it, use the id.
+
+## Sprints
+
+```bash
+atlass jira sprints <id|url|name> [--state active|future|closed ...] [--limit N] [--json]
+```
+
+Lists a board's sprints as `ID  State  Name  Start  End`, active only unless
+`--state` says otherwise. Active sprints come first, then future, then closed
+newest first. The board takes the same forms as `board`.
+
+## Fields
+
+```bash
+atlass jira fields [--search TEXT] [--json]
+```
+
+With no project, `fields` lists every field on the site as `ID  Name  Type`,
+sorted by name. `--search` filters by name or id, ignoring case. The type is the
+custom field's plugin type, such as `float` or `gh-sprint`, or the schema type
+for system fields. `--json` carries the full schema, plugin key included. With a
+project, `fields` shows the create form instead (see Create).
+
 ## Bitbucket
 
 `--repo` takes `workspace/slug` or a bare slug under the configured workspace,

package/dist/bitbucket.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { n as buildStandalone, r as fail } from "./build-DMLlCHdF.mjs";
+import { n as buildStandalone, r as fail } from "./build-H7eTLrf3.mjs";
 //#region src/bitbucket.ts
 buildStandalone("bitbucket").parseAsync().catch(fail);
 //#endregion