Metadata-Version: 2.4
Name: untaped-jira
Version: 11.1.0
Summary: Jira plugin for untaped.
Author: Alexis Beaulieu
Author-email: Alexis Beaulieu <alexisbeaulieu97@gmail.com>
License-Expression: MIT
License-File: LICENSE
Requires-Dist: untaped==11.1.0
Requires-Python: >=3.14.1
Description-Content-Type: text/markdown

# untaped-jira

Install it as part of `untaped`: `uv tool install 'untaped[jira]'` or `pip install 'untaped[jira]'`.
To add it to an existing install, see [Getting started](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/getting-started.md#install).

`untaped jira` searches, creates, updates, comments on and transitions Jira
issues, and looks up projects, boards and sprints, from a terminal, a script
or an agent. It targets Jira Data Center and self-hosted Jira (REST API v2
and Agile 1.0), not Jira Cloud.

## Set up

Create a personal access token in Jira, then:

```bash
untaped config set jira.server.url https://jira.example.com
untaped auth login jira
untaped jira whoami
```

`auth login` stores the token with your password store, not in `config.yml`;
`JIRA_API_TOKEN` also works; see
[Tokens](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/configuration.md#tokens). Defaults such as `jira.default_project` and the
`jira.assigned_jql` base query are in the
[settings](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/reference/config.md#jira).

## Find issues

```bash
untaped jira issues assigned --status 'In Progress' --sprint 'openSprints()'
untaped jira issues search --jql 'project = OPS AND labels = infra ORDER BY created DESC'
untaped jira issues get OPS-123 --comments
```

`issues assigned` narrows your `jira.assigned_jql` base query; pass `--jql`
to `issues search` for an unrestricted query.

## Change issues

```bash
untaped jira issues patch OPS-123 --assignee @me --set-json 'labels=["infra","tls"]' --dry-run
git log -1 --format=%B | untaped jira issues comment OPS-123 --yes
untaped jira issues links create OPS-123 Blocks OPS-124 --dry-run
```

The preview lists each request and one `field: old → new` line per change.
Writes preview and ask first according to `jira.confirm`; `untaped agents jira writes` says which.

## Move issues through a workflow

```bash
untaped jira issues transitions OPS-123
untaped jira issues transition OPS-123 --to Done --dry-run
untaped jira issues search --project OPS --status 'In Review' --format pipe \
  | untaped jira issues transition --stdin --to Done --dry-run
```

Transition names depend on the issue's workflow and current status, so list
them first. A piped batch continues past a failing key.

## Reference

`untaped agents jira` is the full reference, generated by the untaped you run: every command's options, the settings and the guides.

`untaped skills install jira --target claude` (or another [agent](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/skills.md#install-skills)) points your agent at it.

- [Output records](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/reference/records.md#jira) and [exit codes](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/reference/exit-codes.md)
- [Settings](https://github.com/alexisbeaulieu97/untaped/blob/v11.1.0/docs/reference/config.md#jira)
