# Jira Data Center

> Work in Jira on your own servers (Jira Server or Data Center): create, update, move, assign and search issues, comment, attach files, link issues, log work, manage versions and sprints, and start workflows when issues are created, change, move to a status or get comments, and when versions are released or sprints start and close.

App · 25 actions. Web page: https://docs.lodol.com/docs/integrations/jira-data-center

## Actions

### Add attachment

Attach a file to an issue, or attach some text as a text file.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- File (`file`, text): The file to attach: upload one or pick one an earlier step made.
- Text (`text`, text): Text to attach as a text file, instead of a file.
- File name (`file_name`, text): The name to give it, such as notes.txt. Defaults to the file's own name.

**Outputs**

- `author` (text): Who attached it
- `content_url` (text): Where to download it (needs a Jira sign-in)
- `filename` (text): The file's name
- `id` (text): The attachment's id
- `issue_key` (text): The issue it's attached to
- `mime_type` (text): Its type, such as text/plain
- `size` (number): Its size in bytes

**Example output**

```json
{
  "author": "Jane Doe",
  "content_url": "https://jira.example.com/secure/attachment/10230/notes.txt",
  "filename": "notes.txt",
  "id": "10230",
  "issue_key": "WEB-42",
  "mime_type": "text/plain",
  "size": 42
}
```

### Add comment

Add a comment to an issue.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Comment (`body`, text, required): The comment, in Jira's wiki markup or plain text.

**Outputs**

- `author` (text): Who wrote it
- `author_username` (text): The author's username
- `body` (text): Its text
- `created` (text): When it was written
- `id` (text): The comment's id
- `issue_key` (text): The issue it's on
- `link` (text): A link to it in Jira
- `updated` (text): When it was last edited

**Example output**

```json
{
  "author": "Jane Doe",
  "author_username": "jdoe",
  "body": "Reproduced on Firefox too.",
  "created": "2026-11-06T14:12:00.000+0000",
  "id": "20117",
  "issue_key": "WEB-42",
  "link": "https://jira.example.com/browse/WEB-42?focusedCommentId=20117",
  "updated": "2026-11-06T14:12:00.000+0000"
}
```

### Add watcher

Add someone to an issue's watchers, so Jira emails them its changes.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- User (`user`, text, required): The person, by username, or me for the connected user.

**Outputs**

- `issue_key` (text): The issue
- `user` (text): The username added or removed
- `watch_count` (number): How many people watch it now
- `watchers` (list): The usernames watching it now

**Example output**

```json
{
  "issue_key": "WEB-42",
  "user": "jdoe",
  "watch_count": 2,
  "watchers": [
    "jdoe",
    "spatel"
  ]
}
```

### Assign issue

Assign an issue to someone, to the connected user, to the project's default, or to nobody.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Assignee (`assignee`, text, required): A username, me, none to unassign, or automatic for the project's default.

**Outputs**

- `assignee` (text): Who it's assigned to; empty if nobody
- `assignee_username` (text): The assignee's username; empty if nobody
- `components` (list): The names of its components
- `created` (text): When it was created
- `description` (text): Its description
- `due_date` (text): Its due date (YYYY-MM-DD); empty if none
- `fix_versions` (list): The names of the versions it's fixed in
- `id` (text): The issue's id
- `issue_type` (text): Its type, such as Task or Bug
- `key` (text): The issue's key, such as PROJ-123
- `labels` (list): Its labels
- `link` (text): A link to it in Jira
- `parent_key` (text): Its parent's key, for a subtask; empty otherwise
- `priority` (text): Its priority; empty if none
- `project` (text): The name of the project it's in
- `project_key` (text): The key of the project it's in
- `reporter` (text): Who reported it
- `reporter_username` (text): The reporter's username
- `resolution` (text): How it was resolved, such as Done; empty if unresolved
- `resolved` (text): When it was resolved; empty if unresolved
- `status` (text): Its status, such as To Do or In Progress
- `status_category` (text): Its status's category: To Do, In Progress or Done
- `summary` (text): Its one-line summary
- `updated` (text): When it last changed

**Example output**

```json
{
  "assignee": "Jane Doe",
  "assignee_username": "jdoe",
  "components": [
    "Forms"
  ],
  "created": "2026-11-05T09:30:00.000+0000",
  "description": "Submitting the form on /contact shows a spinner and nothing arrives.",
  "due_date": "2026-11-30",
  "fix_versions": [
    "2.4"
  ],
  "id": "10482",
  "issue_type": "Bug",
  "key": "WEB-42",
  "labels": [
    "frontend"
  ],
  "link": "https://jira.example.com/browse/WEB-42",
  "parent_key": "",
  "priority": "High",
  "project": "Website",
  "project_key": "WEB",
  "reporter": "Sam Patel",
  "reporter_username": "spatel",
  "resolution": "",
  "resolved": "",
  "status": "In Progress",
  "status_category": "In Progress",
  "summary": "Contact form does not send",
  "updated": "2026-11-06T14:12:00.000+0000"
}
```

### Create issue

Create an issue in a project, such as a bug from a form or a task from an email.

**Inputs**

- Project (`project`, text, required): The project, by its key such as PROJ.
- Summary (`summary`, text, required): The issue's one-line summary.
- Issue type (`issue_type`, text): What kind of issue, such as Bug. Leave blank for Task, or the project's first type.
- Description (`description`, text): The details, in Jira's wiki markup or plain text.
- Priority (`priority`, text): How urgent it is.
- Assignee (`assignee`, text): Who to assign it to, by username, or me. Leave blank for the project's default.
- Labels (`labels`, list): Labels to put on it, each one word, such as frontend.
- Due date (`due_date`, date): When it's due.
- Components (`components`, list): The project's components it belongs to.
- Fix versions (`fix_versions`, list): The versions it will be fixed in.
- Parent issue (`parent`, text): Make it a subtask of this issue (its key). The issue type must then be a subtask type.
- Other fields (`other_fields`, object): Any other fields by their id, such as customfield_10010: 5. A select field takes {"value": "Option"}.

**Outputs**

- `assignee` (text): Who it's assigned to; empty if nobody
- `assignee_username` (text): The assignee's username; empty if nobody
- `components` (list): The names of its components
- `created` (text): When it was created
- `description` (text): Its description
- `due_date` (text): Its due date (YYYY-MM-DD); empty if none
- `fix_versions` (list): The names of the versions it's fixed in
- `id` (text): The issue's id
- `issue_type` (text): Its type, such as Task or Bug
- `key` (text): The issue's key, such as PROJ-123
- `labels` (list): Its labels
- `link` (text): A link to it in Jira
- `parent_key` (text): Its parent's key, for a subtask; empty otherwise
- `priority` (text): Its priority; empty if none
- `project` (text): The name of the project it's in
- `project_key` (text): The key of the project it's in
- `reporter` (text): Who reported it
- `reporter_username` (text): The reporter's username
- `resolution` (text): How it was resolved, such as Done; empty if unresolved
- `resolved` (text): When it was resolved; empty if unresolved
- `status` (text): Its status, such as To Do or In Progress
- `status_category` (text): Its status's category: To Do, In Progress or Done
- `summary` (text): Its one-line summary
- `updated` (text): When it last changed

**Example output**

```json
{
  "assignee": "Jane Doe",
  "assignee_username": "jdoe",
  "components": [
    "Forms"
  ],
  "created": "2026-11-05T09:30:00.000+0000",
  "description": "Submitting the form on /contact shows a spinner and nothing arrives.",
  "due_date": "2026-11-30",
  "fix_versions": [
    "2.4"
  ],
  "id": "10482",
  "issue_type": "Bug",
  "key": "WEB-42",
  "labels": [
    "frontend"
  ],
  "link": "https://jira.example.com/browse/WEB-42",
  "parent_key": "",
  "priority": "High",
  "project": "Website",
  "project_key": "WEB",
  "reporter": "Sam Patel",
  "reporter_username": "spatel",
  "resolution": "",
  "resolved": "",
  "status": "In Progress",
  "status_category": "In Progress",
  "summary": "Contact form does not send",
  "updated": "2026-11-06T14:12:00.000+0000"
}
```

### Create version

Add a version (a release) to a project.

**Inputs**

- Project (`project`, text, required): The project, by its key such as PROJ.
- Name (`name`, text, required): The version's name, such as 2.4.
- Description (`description`, text): What's in it.
- Release date (`release_date`, date): When it is or was released.
- Released (`released`, true/false): Mark it released already.

**Outputs**

- `archived` (true/false): Whether it's archived
- `description` (text): Its description
- `id` (text): The version's id
- `name` (text): Its name, such as 2.4
- `overdue` (true/false): Whether its release date has passed unreleased
- `project_id` (text): The id of its project
- `release_date` (text): Its release date (YYYY-MM-DD); empty if none
- `released` (true/false): Whether it's released

**Example output**

```json
{
  "archived": false,
  "description": "Contact form fixes",
  "id": "10210",
  "name": "2.4",
  "overdue": false,
  "project_id": "10000",
  "release_date": "2026-11-30",
  "released": false
}
```

### Delete issue

Delete an issue for good, with its comments, attachments and work logged.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Delete subtasks (`delete_subtasks`, true/false): Also delete its subtasks. Jira refuses to delete an issue with subtasks otherwise.

**Outputs**

- `deleted` (true/false): Whether the issue was deleted
- `key` (text): The deleted issue's key

**Example output**

```json
{
  "deleted": true,
  "key": "WEB-42"
}
```

### Delete version

Delete a version. Issues fixed in it or affecting it lose that version.

**Inputs**

- Version (`version`, text, required): The version, by its id.
- Project (`project`, text): The project the version is in, to pick the version from a list.

**Outputs**

- `deleted` (true/false): Whether the version was deleted
- `version_id` (text): The deleted version's id

**Example output**

```json
{
  "deleted": true,
  "version_id": "10210"
}
```

### Find users

Find people by part of their username, name or email, to get the username other steps take.

**Inputs**

- Search (`query`, text, required): Part of a username, name or email.
- How many (`max_results`, number): The most to return, up to 100. Defaults to 25. From 1 to 100.

**Outputs**

- `count` (number): How many were found
- `users` (list): The people found

**Example output**

```json
{
  "count": 1,
  "users": [
    {
      "active": true,
      "display_name": "Jane Doe",
      "email": "jane@example.com",
      "key": "JIRAUSER10100",
      "time_zone": "Europe/London",
      "username": "jdoe"
    }
  ]
}
```

### Get issue

Get an issue's fields, with the transitions the connected user can make on it now.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.

**Outputs**

- `assignee` (text): Who it's assigned to; empty if nobody
- `assignee_username` (text): The assignee's username; empty if nobody
- `components` (list): The names of its components
- `created` (text): When it was created
- `description` (text): Its description
- `due_date` (text): Its due date (YYYY-MM-DD); empty if none
- `fix_versions` (list): The names of the versions it's fixed in
- `id` (text): The issue's id
- `issue_type` (text): Its type, such as Task or Bug
- `key` (text): The issue's key, such as PROJ-123
- `labels` (list): Its labels
- `link` (text): A link to it in Jira
- `parent_key` (text): Its parent's key, for a subtask; empty otherwise
- `priority` (text): Its priority; empty if none
- `project` (text): The name of the project it's in
- `project_key` (text): The key of the project it's in
- `reporter` (text): Who reported it
- `reporter_username` (text): The reporter's username
- `resolution` (text): How it was resolved, such as Done; empty if unresolved
- `resolved` (text): When it was resolved; empty if unresolved
- `status` (text): Its status, such as To Do or In Progress
- `status_category` (text): Its status's category: To Do, In Progress or Done
- `summary` (text): Its one-line summary
- `transitions` (list): The transitions the connected user can make on it now
- `updated` (text): When it last changed

**Example output**

```json
{
  "assignee": "Jane Doe",
  "assignee_username": "jdoe",
  "components": [
    "Forms"
  ],
  "created": "2026-11-05T09:30:00.000+0000",
  "description": "Submitting the form on /contact shows a spinner and nothing arrives.",
  "due_date": "2026-11-30",
  "fix_versions": [
    "2.4"
  ],
  "id": "10482",
  "issue_type": "Bug",
  "key": "WEB-42",
  "labels": [
    "frontend"
  ],
  "link": "https://jira.example.com/browse/WEB-42",
  "parent_key": "",
  "priority": "High",
  "project": "Website",
  "project_key": "WEB",
  "reporter": "Sam Patel",
  "reporter_username": "spatel",
  "resolution": "",
  "resolved": "",
  "status": "In Progress",
  "status_category": "In Progress",
  "summary": "Contact form does not send",
  "transitions": [
    {
      "id": "31",
      "name": "Done",
      "to_status": "Done"
    },
    {
      "id": "11",
      "name": "Stop Progress",
      "to_status": "To Do"
    }
  ],
  "updated": "2026-11-06T14:12:00.000+0000"
}
```

### Link issues

Link two issues, such as one blocking another or duplicating it.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Relationship (`relationship`, text, required): How the first issue relates to the other, in your Jira's words, such as blocks or relates to.
- Other issue (`other_issue`, text, required): The issue to link it to: its key or link.
- Comment (`comment`, text): A comment to add to the first issue with the link.

**Outputs**

- `issue_key` (text): The first issue
- `link_type` (text): The link type, such as Blocks
- `other_issue_key` (text): The issue it's linked to
- `relationship` (text): How the first issue relates to the other, such as blocks

**Example output**

```json
{
  "issue_key": "WEB-42",
  "link_type": "Blocks",
  "other_issue_key": "WEB-43",
  "relationship": "blocks"
}
```

### List boards

List the Scrum and Kanban boards the connected user can see.

**Inputs**

- Project (`project`, text): Only boards for this project. Leave blank for every board.
- Board type (`board_type`, text): Only Scrum or only Kanban boards. Leave blank for both. One of: `scrum`, `kanban`.
- Name (`name`, text): Only boards whose name contains this.

**Outputs**

- `boards` (list): The boards
- `count` (number): How many there are

**Example output**

```json
{
  "boards": [
    {
      "id": 84,
      "name": "WEB board",
      "type": "scrum"
    }
  ],
  "count": 1
}
```

### List comments

List an issue's newest comments, oldest of them first.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- How many (`max_results`, number): The most to return, up to 100. Defaults to 25. From 1 to 100.

**Outputs**

- `comments` (list): The newest comments, oldest of them first
- `count` (number): How many are listed here
- `issue_key` (text): The issue
- `total` (number): How many comments the issue has

**Example output**

```json
{
  "comments": [
    {
      "author": "Jane Doe",
      "author_username": "jdoe",
      "body": "Reproduced on Firefox too.",
      "created": "2026-11-06T14:12:00.000+0000",
      "id": "20117",
      "issue_key": "WEB-42",
      "link": "https://jira.example.com/browse/WEB-42?focusedCommentId=20117",
      "updated": "2026-11-06T14:12:00.000+0000"
    }
  ],
  "count": 1,
  "issue_key": "WEB-42",
  "total": 1
}
```

### List components

List a project's components, with their leads.

**Inputs**

- Project (`project`, text, required): The project, by its key such as PROJ.

**Outputs**

- `components` (list): The components
- `count` (number): How many there are
- `project` (text): The project

**Example output**

```json
{
  "components": [
    {
      "description": "Contact and sign-up forms",
      "id": "10300",
      "lead": "Jane Doe",
      "lead_username": "jdoe",
      "name": "Forms"
    }
  ],
  "count": 1,
  "project": "WEB"
}
```

### List projects

List the projects the connected user can see, or those on one board.

**Inputs**

- Board (`board`, text): Only the projects on this board. Leave blank for every project.

**Outputs**

- `count` (number): How many there are
- `projects` (list): The projects

**Example output**

```json
{
  "count": 1,
  "projects": [
    {
      "id": "10000",
      "key": "WEB",
      "link": "https://jira.example.com/browse/WEB",
      "name": "Website",
      "project_type": "software"
    }
  ]
}
```

### List sprints

List a Scrum board's sprints, active, future or closed.

**Inputs**

- Board (`board`, text, required): The board, by its id.
- States (`states`, list): Only sprints in these states. Leave blank for all. One or more of: `active`, `future`, `closed`.

**Outputs**

- `board_id` (number): The board
- `count` (number): How many are listed
- `sprints` (list): The sprints, closed first, then active, then future

**Example output**

```json
{
  "board_id": 84,
  "count": 1,
  "sprints": [
    {
      "board_id": 84,
      "complete_date": "",
      "end_date": "2026-11-16T17:00:00.000+00:00",
      "goal": "Ship the new contact form",
      "id": 37,
      "name": "WEB Sprint 12",
      "start_date": "2026-11-02T09:00:00.000+00:00",
      "state": "active"
    }
  ]
}
```

### List versions

List a project's versions, released, unreleased or both.

**Inputs**

- Project (`project`, text, required): The project, by its key such as PROJ.
- Which (`status`, text): Released versions, unreleased ones, or all. Defaults to all. One of: `all`, `released`, `unreleased`.
- Include archived (`include_archived`, true/false): Also list archived versions.

**Outputs**

- `count` (number): How many are listed
- `project` (text): The project
- `versions` (list): The versions, in the project's order

**Example output**

```json
{
  "count": 1,
  "project": "WEB",
  "versions": [
    {
      "archived": false,
      "description": "Contact form fixes",
      "id": "10210",
      "name": "2.4",
      "overdue": false,
      "project_id": "10000",
      "release_date": "2026-11-30",
      "released": false
    }
  ]
}
```

### List work logs

List the time logged on an issue, with the total.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.

**Outputs**

- `count` (number): How many work logs it has
- `issue_key` (text): The issue
- `total_seconds` (number): All the time logged, in seconds
- `worklogs` (list): The work logged on it

**Example output**

```json
{
  "count": 1,
  "issue_key": "WEB-42",
  "total_seconds": 5400,
  "worklogs": [
    {
      "author": "Jane Doe",
      "author_username": "jdoe",
      "comment": "Traced it to the mail relay.",
      "created": "2026-11-06T10:31:00.000+0000",
      "id": "10077",
      "issue_key": "WEB-42",
      "started": "2026-11-06T09:00:00.000+0000",
      "time_spent": "1h 30m",
      "time_spent_seconds": 5400
    }
  ]
}
```

### Log work

Log time spent on an issue, with what was done.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Time spent (`time_spent`, text, required): How long, in Jira's words, such as 30m, 1h 30m or 2d.
- Started (`started`, date and time): When the work started. Leave blank for now.
- Comment (`comment`, text): What was done.

**Outputs**

- `author` (text): Who logged it
- `author_username` (text): Their username
- `comment` (text): What was done
- `created` (text): When it was logged
- `id` (text): The work log's id
- `issue_key` (text): The issue it's on
- `started` (text): When the work started
- `time_spent` (text): The time, in Jira's words, such as 1h 30m
- `time_spent_seconds` (number): The time in seconds

**Example output**

```json
{
  "author": "Jane Doe",
  "author_username": "jdoe",
  "comment": "Traced it to the mail relay.",
  "created": "2026-11-06T10:31:00.000+0000",
  "id": "10077",
  "issue_key": "WEB-42",
  "started": "2026-11-06T09:00:00.000+0000",
  "time_spent": "1h 30m",
  "time_spent_seconds": 5400
}
```

### Move issues to sprint

Move up to 50 issues into an active or future sprint.

**Inputs**

- Sprint (`sprint`, text, required): The sprint, by its id. Pick a board first to choose from its sprints.
- Issues (`issues`, list, required): The keys of the issues to move, such as PROJ-123.
- Board (`board`, text): The sprint's board, to pick the sprint from a list.

**Outputs**

- `count` (number): How many were moved
- `issues` (list): The keys of the issues moved
- `sprint_id` (number): The sprint

**Example output**

```json
{
  "count": 1,
  "issues": [
    "WEB-42"
  ],
  "sprint_id": 37
}
```

### Remove watcher

Remove someone from an issue's watchers.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- User (`user`, text, required): The person, by username, or me for the connected user.

**Outputs**

- `issue_key` (text): The issue
- `user` (text): The username added or removed
- `watch_count` (number): How many people watch it now
- `watchers` (list): The usernames watching it now

**Example output**

```json
{
  "issue_key": "WEB-42",
  "user": "jdoe",
  "watch_count": 1,
  "watchers": [
    "spatel"
  ]
}
```

### Search issues

Find issues with a JQL search, the same search Jira's advanced issue search uses.

**Inputs**

- JQL (`jql`, text, required): The search, such as project = PROJ AND status = "In Progress" ORDER BY updated DESC.
- How many (`max_results`, number): The most to return, up to 100. Defaults to 25. From 1 to 100.
- Start at (`start_at`, number): How many results to skip, for the next page. Defaults to 0. At least 0.

**Outputs**

- `count` (number): How many are listed here
- `issues` (list): The issues found, in the search's order
- `start_at` (number): Where in the results this page starts, from 0
- `total` (number): How many match in all

**Example output**

```json
{
  "count": 1,
  "issues": [
    {
      "assignee": "Jane Doe",
      "assignee_username": "jdoe",
      "components": [
        "Forms"
      ],
      "created": "2026-11-05T09:30:00.000+0000",
      "description": "Submitting the form on /contact shows a spinner and nothing arrives.",
      "due_date": "2026-11-30",
      "fix_versions": [
        "2.4"
      ],
      "id": "10482",
      "issue_type": "Bug",
      "key": "WEB-42",
      "labels": [
        "frontend"
      ],
      "link": "https://jira.example.com/browse/WEB-42",
      "parent_key": "",
      "priority": "High",
      "project": "Website",
      "project_key": "WEB",
      "reporter": "Sam Patel",
      "reporter_username": "spatel",
      "resolution": "",
      "resolved": "",
      "status": "In Progress",
      "status_category": "In Progress",
      "summary": "Contact form does not send",
      "updated": "2026-11-06T14:12:00.000+0000"
    }
  ],
  "start_at": 0,
  "total": 1
}
```

### Transition issue

Move an issue through its workflow, such as from To Do to In Progress, with an optional comment.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Transition (`transition`, text, required): The move to make: pick one, or type its name or the status it leads to.
- Comment (`comment`, text): A comment to add as it moves.
- Resolution (`resolution`, text): A resolution such as Done or Won't Do, when the move's screen asks for one.

**Outputs**

- `assignee` (text): Who it's assigned to; empty if nobody
- `assignee_username` (text): The assignee's username; empty if nobody
- `components` (list): The names of its components
- `created` (text): When it was created
- `description` (text): Its description
- `due_date` (text): Its due date (YYYY-MM-DD); empty if none
- `fix_versions` (list): The names of the versions it's fixed in
- `id` (text): The issue's id
- `issue_type` (text): Its type, such as Task or Bug
- `key` (text): The issue's key, such as PROJ-123
- `labels` (list): Its labels
- `link` (text): A link to it in Jira
- `parent_key` (text): Its parent's key, for a subtask; empty otherwise
- `priority` (text): Its priority; empty if none
- `project` (text): The name of the project it's in
- `project_key` (text): The key of the project it's in
- `reporter` (text): Who reported it
- `reporter_username` (text): The reporter's username
- `resolution` (text): How it was resolved, such as Done; empty if unresolved
- `resolved` (text): When it was resolved; empty if unresolved
- `status` (text): Its status, such as To Do or In Progress
- `status_category` (text): Its status's category: To Do, In Progress or Done
- `summary` (text): Its one-line summary
- `transition` (text): The transition made
- `updated` (text): When it last changed

**Example output**

```json
{
  "assignee": "Jane Doe",
  "assignee_username": "jdoe",
  "components": [
    "Forms"
  ],
  "created": "2026-11-05T09:30:00.000+0000",
  "description": "Submitting the form on /contact shows a spinner and nothing arrives.",
  "due_date": "2026-11-30",
  "fix_versions": [
    "2.4"
  ],
  "id": "10482",
  "issue_type": "Bug",
  "key": "WEB-42",
  "labels": [
    "frontend"
  ],
  "link": "https://jira.example.com/browse/WEB-42",
  "parent_key": "",
  "priority": "High",
  "project": "Website",
  "project_key": "WEB",
  "reporter": "Sam Patel",
  "reporter_username": "spatel",
  "resolution": "Done",
  "resolved": "",
  "status": "Done",
  "status_category": "Done",
  "summary": "Contact form does not send",
  "transition": "Done",
  "updated": "2026-11-06T14:12:00.000+0000"
}
```

### Update issue

Change an issue's summary, description, priority, labels, due date, components, fix versions or other fields. Fields left blank keep their value.

**Inputs**

- Issue (`issue`, text, required): The issue's key, such as PROJ-123, or its link.
- Summary (`summary`, text): A new one-line summary.
- Description (`description`, text): A new description, replacing the old one.
- Priority (`priority`, text): How urgent it is.
- Labels (`labels`, list): Labels to replace its labels with, each one word.
- Due date (`due_date`, date): When it's due.
- Components (`components`, list): Components to replace its components with, by name or id.
- Fix versions (`fix_versions`, list): Versions to replace its fix versions with, by name or id.
- Other fields (`other_fields`, object): Any other fields by their id, such as customfield_10010: 5. A select field takes {"value": "Option"}.

**Outputs**

- `assignee` (text): Who it's assigned to; empty if nobody
- `assignee_username` (text): The assignee's username; empty if nobody
- `components` (list): The names of its components
- `created` (text): When it was created
- `description` (text): Its description
- `due_date` (text): Its due date (YYYY-MM-DD); empty if none
- `fix_versions` (list): The names of the versions it's fixed in
- `id` (text): The issue's id
- `issue_type` (text): Its type, such as Task or Bug
- `key` (text): The issue's key, such as PROJ-123
- `labels` (list): Its labels
- `link` (text): A link to it in Jira
- `parent_key` (text): Its parent's key, for a subtask; empty otherwise
- `priority` (text): Its priority; empty if none
- `project` (text): The name of the project it's in
- `project_key` (text): The key of the project it's in
- `reporter` (text): Who reported it
- `reporter_username` (text): The reporter's username
- `resolution` (text): How it was resolved, such as Done; empty if unresolved
- `resolved` (text): When it was resolved; empty if unresolved
- `status` (text): Its status, such as To Do or In Progress
- `status_category` (text): Its status's category: To Do, In Progress or Done
- `summary` (text): Its one-line summary
- `updated` (text): When it last changed

**Example output**

```json
{
  "assignee": "Jane Doe",
  "assignee_username": "jdoe",
  "components": [
    "Forms"
  ],
  "created": "2026-11-05T09:30:00.000+0000",
  "description": "Submitting the form on /contact shows a spinner and nothing arrives.",
  "due_date": "2026-11-30",
  "fix_versions": [
    "2.4"
  ],
  "id": "10482",
  "issue_type": "Bug",
  "key": "WEB-42",
  "labels": [
    "frontend"
  ],
  "link": "https://jira.example.com/browse/WEB-42",
  "parent_key": "",
  "priority": "High",
  "project": "Website",
  "project_key": "WEB",
  "reporter": "Sam Patel",
  "reporter_username": "spatel",
  "resolution": "",
  "resolved": "",
  "status": "In Progress",
  "status_category": "In Progress",
  "summary": "Contact form does not send",
  "updated": "2026-11-06T14:12:00.000+0000"
}
```

### Update version

Rename a version, change its release date, or release or archive it.

**Inputs**

- Version (`version`, text, required): The version, by its id.
- Project (`project`, text): The project the version is in, to pick the version from a list.
- Name (`name`, text): A new name.
- Description (`description`, text): A new description.
- Release date (`release_date`, date): When it is or was released.
- Released (`released`, true/false): Turn on to release it, off to unrelease it.
- Archived (`archived`, true/false): Turn on to archive it, off to restore it.

**Outputs**

- `archived` (true/false): Whether it's archived
- `description` (text): Its description
- `id` (text): The version's id
- `name` (text): Its name, such as 2.4
- `overdue` (true/false): Whether its release date has passed unreleased
- `project_id` (text): The id of its project
- `release_date` (text): Its release date (YYYY-MM-DD); empty if none
- `released` (true/false): Whether it's released

**Example output**

```json
{
  "archived": false,
  "description": "Contact form fixes",
  "id": "10210",
  "name": "2.4",
  "overdue": false,
  "project_id": "10000",
  "release_date": "2026-11-30",
  "released": true
}
```
