workflow issues

List a view’s issues, as the Issues pane lists them

Synopsis

List the issues of one of jira.views — the first when –view names none, or the issues assigned to you when none is configured — one a line: the key, the summary and the status. A view is scoped to you unless its query names the assignee, as the interfaces scope it. Only the first page is read: the view’s first 50 issues and, on the first view when issues.forge is on, the issues assigned to you on the repository’s forge ahead of them. A longer list is noted on stderr, and –json carries its total, the forge’s issues counted in it. –json prints the web API’s page of issues.

workflow issues [flags]

Examples

  workflow issues --view Sprint
  workflow issues --json | jq -r '.issues[].key'   # the keys alone

Options

  -h, --help          help for issues
  -j, --json          print the page of issues as JSON
      --view string   the view to list, by its name in jira.views; the first when not given

Options inherited from parent commands

  -n, --dry-run             hold back every write to Jira, the forge, the messaging service, Taskwarrior, git and files, and say what it would have done
      --log-format FORMAT   say what goes to stderr as FORMAT: text, or json or logfmt, an entry a line stamped with its time (default text)
  -q, --quiet               say only warnings, errors and questions on stderr, leaving every note out
      --request-log FILE    append a one-line outline of each request (method, path, status, duration) to FILE, for a bug report
      --verbose             also say each request's outline on stderr, as a debug line (not while the terminal interface draws)

SEE ALSO

• workflow - Run your Jira, Git forge and messaging workflow, in the terminal or a browser