atlass 2.1.0 → 2.3.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
@@ -103,10 +103,26 @@ line, or the first `## Comments` or `## Attachments` in older copies.
103
103
  overwriting.
104
104
  - Confluence uploads local images referenced in the body as attachments. Jira
105
105
  update does not support image changes yet.
106
+ - Embedded videos are set to the full width of the text column. Images keep
107
+ their natural size.
106
108
  - After an update, the new `updated` (and for Confluence, `version`, and `title`
107
109
  with `--title`) is written back to the frontmatter, so the file can be pushed
108
110
  again without a fresh copy.
109
111
 
112
+ ## Attach
113
+
114
+ ```bash
115
+ atlass jira attach PROJ-123 screenshot.png logs.zip
116
+ atlass confluence attach 123456 diagram.png --comment "v2 layout"
117
+ ```
118
+
119
+ Uploads files as new attachments, one request per file. Every file is read
120
+ before anything uploads, and the first failed upload stops the run. `--json`
121
+ prints the filename, id, and size of each attachment.
122
+
123
+ Jira keeps duplicate filenames side by side. Confluence refuses a filename the
124
+ page already has, checked before any upload. `--comment` is Confluence only.
125
+
110
126
  ## Create
111
127
 
112
128
  ```bash
@@ -157,6 +173,7 @@ atlass confluence list --space DOCS
157
173
  `jira list` shows issues assigned to you as `KEY Status Age Summary`, with
158
174
  In Progress first, then To Do, and the most recently updated at the top of each
159
175
  group. Done issues are left out; `--all` adds those updated in the last 30 days.
176
+ `--limit` keeps the first rows of that order; without it, all are shown.
160
177
 
161
178
  `confluence list` shows the pages you starred as `ID SPACE Age Title`, most
162
179
  recently updated first. `--limit` works as for search. Star or unstar a page
@@ -175,10 +192,12 @@ atlass confluence search "onboarding" --space DOCS --label runbook
175
192
  ```
176
193
 
177
194
  Jira filters on `--project`, `--assignee`, `--reporter`, `--status`, `--type`,
178
- `--label`, `--updated` and `--open`; Confluence on `--space`, `--label`,
179
- `--updated` and `--starred`. Repeating a flag matches any of its values;
180
- different flags must all match. `--assignee` and `--reporter` take `me`, an
181
- account id, or a name to look up. `--updated` takes `7d`, `2w`, `3m` or
195
+ `--label`, `--sprint`, `--updated` and `--open`; Confluence on `--space`,
196
+ `--label`, `--updated` and `--starred`. Repeating a flag matches any of its
197
+ values; different flags must all match. `--assignee` and `--reporter` take `me`,
198
+ an account id, or a name to look up. `--sprint` takes `active`, `future`, a
199
+ sprint id, or a sprint name; names can repeat across boards, an id cannot.
200
+ `--updated` takes `7d`, `2w`, `3m` or
182
201
  `YYYY-MM-DD`. Results sort by most recently updated and use the same columns
183
202
  as `jira list` and `confluence list`.
184
203
 
@@ -193,6 +212,19 @@ atlass confluence cql "label = runbook AND creator = currentUser()"
193
212
  to pick results interactively and copy each one, with `--out` as the target
194
213
  directory. All four work on both search commands.
195
214
 
215
+ `--field` adds a field's value to each issue on `jira search`, `jira jql` and
216
+ `jira list`:
217
+
218
+ ```bash
219
+ atlass jira search --assignee me --status Closed --field "Story Points" --json
220
+ ```
221
+
222
+ It takes a field id or a name, ignoring case, and repeats for more fields. A
223
+ name several fields share fails and lists their ids; `atlass jira fields
224
+ --search` finds the one you want. Each field becomes a column after the status.
225
+ With `--json`, each issue gains a `fields` object of raw values keyed by the
226
+ name you passed.
227
+
196
228
  Discovery aids for the filters:
197
229
 
198
230
  ```bash
@@ -200,6 +232,42 @@ atlass jira projects [query]
200
232
  atlass jira statuses [query] [--project PROJ]
201
233
  ```
202
234
 
235
+ ## Boards
236
+
237
+ ```bash
238
+ atlass jira boards [query] [--project PROJ]
239
+ atlass jira board <id|url|name> [--json]
240
+ ```
241
+
242
+ `boards` lists every board as `ID Type Name Project`, filtered by name and
243
+ project key. Boards that span projects leave the project cell empty.
244
+
245
+ `board` shows one board: the field it estimates with, its filter JQL, and each
246
+ column's statuses with their categories. A name must match exactly, ignoring
247
+ case; if several boards share it, use the id.
248
+
249
+ ## Sprints
250
+
251
+ ```bash
252
+ atlass jira sprints <id|url|name> [--state active|future|closed ...] [--limit N] [--json]
253
+ ```
254
+
255
+ Lists a board's sprints as `ID State Name Start End`, active only unless
256
+ `--state` says otherwise. Active sprints come first, then future, then closed
257
+ newest first. The board takes the same forms as `board`.
258
+
259
+ ## Fields
260
+
261
+ ```bash
262
+ atlass jira fields [--search TEXT] [--json]
263
+ ```
264
+
265
+ With no project, `fields` lists every field on the site as `ID Name Type`,
266
+ sorted by name. `--search` filters by name or id, ignoring case. The type is the
267
+ custom field's plugin type, such as `float` or `gh-sprint`, or the schema type
268
+ for system fields. `--json` carries the full schema, plugin key included. With a
269
+ project, `fields` shows the create form instead (see Create).
270
+
203
271
  ## Bitbucket
204
272
 
205
273
  `--repo` takes `workspace/slug` or a bare slug under the configured workspace,
@@ -1,5 +1,5 @@
1
1
  #!/usr/bin/env node
2
- import { n as buildStandalone, r as fail } from "./build-_4VuIcqF.mjs";
2
+ import { n as buildStandalone, r as fail } from "./build-6PhpYMjp.mjs";
3
3
  //#region src/bitbucket.ts
4
4
  buildStandalone("bitbucket").parseAsync().catch(fail);
5
5
  //#endregion