You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--json on user search/view, meta … and issue transitions prints the views' JSON (people as accountId, name, email…; a transition's to is its status name) instead of Jira's raw responses.
--json on project, board, sprint, filter, field and dashboard commands prints the views' JSON (camelCase, people as {accountId, name, email}) instead of Jira's raw responses. Every write now asks first: project update/restore, sprint update/start/add/remove, filter update/star/columns and field update/restore take --yes in scripts, and a declined change exits 2 instead of 1.
the parts' --json output uses the views' shapes; comment edit and comment add --edit-last now ask (pass --yes); worklog add takes --time for many issues (KEY TIME still works).
audit.jsonl lines now hold "changes" (key, before, after per issue) and "failed" instead of top-level "before"/"after", and a declined confirmation exits 2 instead of 1.
issue transition asks before moving even a single issue, and refuses without --yes when there is no terminal to ask on (scripts must pass --yes).
acli-py issue view --json prints the issue view (key, summary, status {name, category}, assignee {accountId, name, email}, links, comments {total, items}, extra fields under "fields") instead of Jira's raw JSON.
the aj command is no longer installed; use acli-py.