Jira Data Center
App · 25 actions
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.
Actions
| Action | What it does |
|---|---|
| Add attachment | Attach a file to an issue, or attach some text as a text file. |
| Add comment | Add a comment to an issue. |
| Add watcher | Add someone to an issue's watchers, so Jira emails them its changes. |
| Assign issue | Assign an issue to someone, to the connected user, to the project's default, or to nobody. |
| Create issue | Create an issue in a project, such as a bug from a form or a task from an email. |
| Create version | Add a version (a release) to a project. |
| Delete issue | Delete an issue for good, with its comments, attachments and work logged. |
| Delete version | Delete a version. |
| Find users | Find people by part of their username, name or email, to get the username other steps take. |
| Get issue | Get an issue's fields, with the transitions the connected user can make on it now. |
| Link issues | Link two issues, such as one blocking another or duplicating it. |
| List boards | List the Scrum and Kanban boards the connected user can see. |
| List comments | List an issue's newest comments, oldest of them first. |
| List components | List a project's components, with their leads. |
| List projects | List the projects the connected user can see, or those on one board. |
| List sprints | List a Scrum board's sprints, active, future or closed. |
| List versions | List a project's versions, released, unreleased or both. |
| List work logs | List the time logged on an issue, with the total. |
| Log work | Log time spent on an issue, with what was done. |
| Move issues to sprint | Move up to 50 issues into an active or future sprint. |
| Remove watcher | Remove someone from an issue's watchers. |
| Search issues | Find issues with a JQL search, the same search Jira's advanced issue search uses. |
| Transition issue | Move an issue through its workflow, such as from To Do to In Progress, with an optional comment. |
| Update issue | Change an issue's summary, description, priority, labels, due date, components, fix versions or other fields. |
| Update version | Rename a version, change its release date, or release or archive it. |
Add attachment
Attach a file to an issue, or attach some text as a text file.
Inputs
- Issue
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- File
filetext - The file to attach: upload one or pick one an earlier step made.
- Text
texttext - Text to attach as a text file, instead of a file.
- File name
file_nametext - The name to give it, such as notes.txt. Defaults to the file's own name.
Outputs
authortext- Who attached it
content_urltext- Where to download it (needs a Jira sign-in)
filenametext- The file's name
idtext- The attachment's id
issue_keytext- The issue it's attached to
mime_typetext- Its type, such as text/plain
sizenumber- Its size in bytes
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Comment
bodytextRequired - The comment, in Jira's wiki markup or plain text.
Outputs
authortext- Who wrote it
author_usernametext- The author's username
bodytext- Its text
createdtext- When it was written
idtext- The comment's id
issue_keytext- The issue it's on
linktext- A link to it in Jira
updatedtext- When it was last edited
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- User
usertextRequired - The person, by username, or me for the connected user.
Outputs
issue_keytext- The issue
usertext- The username added or removed
watch_countnumber- How many people watch it now
watcherslist- The usernames watching it now
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Assignee
assigneetextRequired - A username, me, none to unassign, or automatic for the project's default.
Outputs
assigneetext- Who it's assigned to; empty if nobody
assignee_usernametext- The assignee's username; empty if nobody
componentslist- The names of its components
createdtext- When it was created
descriptiontext- Its description
due_datetext- Its due date (YYYY-MM-DD); empty if none
fix_versionslist- The names of the versions it's fixed in
idtext- The issue's id
issue_typetext- Its type, such as Task or Bug
keytext- The issue's key, such as PROJ-123
labelslist- Its labels
linktext- A link to it in Jira
parent_keytext- Its parent's key, for a subtask; empty otherwise
prioritytext- Its priority; empty if none
projecttext- The name of the project it's in
project_keytext- The key of the project it's in
reportertext- Who reported it
reporter_usernametext- The reporter's username
resolutiontext- How it was resolved, such as Done; empty if unresolved
resolvedtext- When it was resolved; empty if unresolved
statustext- Its status, such as To Do or In Progress
status_categorytext- Its status's category: To Do, In Progress or Done
summarytext- Its one-line summary
updatedtext- When it last changed
Example output
{
"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
projecttextRequired - The project, by its key such as PROJ.
- Summary
summarytextRequired - The issue's one-line summary.
- Issue type
issue_typetext - What kind of issue, such as Bug. Leave blank for Task, or the project's first type.
- Description
descriptiontext - The details, in Jira's wiki markup or plain text.
- Priority
prioritytext - How urgent it is.
- Assignee
assigneetext - Who to assign it to, by username, or me. Leave blank for the project's default.
- Labels
labelslist - Labels to put on it, each one word, such as frontend.
- Due date
due_datedate - When it's due.
- Components
componentslist - The project's components it belongs to.
- Fix versions
fix_versionslist - The versions it will be fixed in.
- Parent issue
parenttext - Make it a subtask of this issue (its key). The issue type must then be a subtask type.
- Other fields
other_fieldsobject - Any other fields by their id, such as customfield_10010: 5. A select field takes {"value": "Option"}.
Outputs
assigneetext- Who it's assigned to; empty if nobody
assignee_usernametext- The assignee's username; empty if nobody
componentslist- The names of its components
createdtext- When it was created
descriptiontext- Its description
due_datetext- Its due date (YYYY-MM-DD); empty if none
fix_versionslist- The names of the versions it's fixed in
idtext- The issue's id
issue_typetext- Its type, such as Task or Bug
keytext- The issue's key, such as PROJ-123
labelslist- Its labels
linktext- A link to it in Jira
parent_keytext- Its parent's key, for a subtask; empty otherwise
prioritytext- Its priority; empty if none
projecttext- The name of the project it's in
project_keytext- The key of the project it's in
reportertext- Who reported it
reporter_usernametext- The reporter's username
resolutiontext- How it was resolved, such as Done; empty if unresolved
resolvedtext- When it was resolved; empty if unresolved
statustext- Its status, such as To Do or In Progress
status_categorytext- Its status's category: To Do, In Progress or Done
summarytext- Its one-line summary
updatedtext- When it last changed
Example output
{
"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
projecttextRequired - The project, by its key such as PROJ.
- Name
nametextRequired - The version's name, such as 2.4.
- Description
descriptiontext - What's in it.
- Release date
release_datedate - When it is or was released.
- Released
releasedtrue/false - Mark it released already.
Outputs
archivedtrue/false- Whether it's archived
descriptiontext- Its description
idtext- The version's id
nametext- Its name, such as 2.4
overduetrue/false- Whether its release date has passed unreleased
project_idtext- The id of its project
release_datetext- Its release date (YYYY-MM-DD); empty if none
releasedtrue/false- Whether it's released
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Delete subtasks
delete_subtaskstrue/false - Also delete its subtasks. Jira refuses to delete an issue with subtasks otherwise.
Outputs
deletedtrue/false- Whether the issue was deleted
keytext- The deleted issue's key
Example output
{
"deleted": true,
"key": "WEB-42"
}Delete version
Delete a version. Issues fixed in it or affecting it lose that version.
Inputs
- Version
versiontextRequired - The version, by its id.
- Project
projecttext - The project the version is in, to pick the version from a list.
Outputs
deletedtrue/false- Whether the version was deleted
version_idtext- The deleted version's id
Example output
{
"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
querytextRequired - Part of a username, name or email.
- How many
max_resultsnumber - The most to return, up to 100. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many were found
userslist- The people found
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
Outputs
assigneetext- Who it's assigned to; empty if nobody
assignee_usernametext- The assignee's username; empty if nobody
componentslist- The names of its components
createdtext- When it was created
descriptiontext- Its description
due_datetext- Its due date (YYYY-MM-DD); empty if none
fix_versionslist- The names of the versions it's fixed in
idtext- The issue's id
issue_typetext- Its type, such as Task or Bug
keytext- The issue's key, such as PROJ-123
labelslist- Its labels
linktext- A link to it in Jira
parent_keytext- Its parent's key, for a subtask; empty otherwise
prioritytext- Its priority; empty if none
projecttext- The name of the project it's in
project_keytext- The key of the project it's in
reportertext- Who reported it
reporter_usernametext- The reporter's username
resolutiontext- How it was resolved, such as Done; empty if unresolved
resolvedtext- When it was resolved; empty if unresolved
statustext- Its status, such as To Do or In Progress
status_categorytext- Its status's category: To Do, In Progress or Done
summarytext- Its one-line summary
transitionslist- The transitions the connected user can make on it now
updatedtext- When it last changed
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Relationship
relationshiptextRequired - How the first issue relates to the other, in your Jira's words, such as blocks or relates to.
- Other issue
other_issuetextRequired - The issue to link it to: its key or link.
- Comment
commenttext - A comment to add to the first issue with the link.
Outputs
issue_keytext- The first issue
link_typetext- The link type, such as Blocks
other_issue_keytext- The issue it's linked to
relationshiptext- How the first issue relates to the other, such as blocks
Example output
{
"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
projecttext - Only boards for this project. Leave blank for every board.
- Board type
board_typetext - Only Scrum or only Kanban boards. Leave blank for both.One of:
scrum,kanban. - Name
nametext - Only boards whose name contains this.
Outputs
boardslist- The boards
countnumber- How many there are
Example output
{
"boards": [
{
"id": 84,
"name": "WEB board",
"type": "scrum"
}
],
"count": 1
}List comments
List an issue's newest comments, oldest of them first.
Inputs
- Issue
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- How many
max_resultsnumber - The most to return, up to 100. Defaults to 25.From 1 to 100.
Outputs
commentslist- The newest comments, oldest of them first
countnumber- How many are listed here
issue_keytext- The issue
totalnumber- How many comments the issue has
Example output
{
"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
projecttextRequired - The project, by its key such as PROJ.
Outputs
componentslist- The components
countnumber- How many there are
projecttext- The project
Example output
{
"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
boardtext - Only the projects on this board. Leave blank for every project.
Outputs
countnumber- How many there are
projectslist- The projects
Example output
{
"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
boardtextRequired - The board, by its id.
- States
stateslist - Only sprints in these states. Leave blank for all.One or more of:
active,future,closed.
Outputs
board_idnumber- The board
countnumber- How many are listed
sprintslist- The sprints, closed first, then active, then future
Example output
{
"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
projecttextRequired - The project, by its key such as PROJ.
- Which
statustext - Released versions, unreleased ones, or all. Defaults to all.One of:
all,released,unreleased. - Include archived
include_archivedtrue/false - Also list archived versions.
Outputs
countnumber- How many are listed
projecttext- The project
versionslist- The versions, in the project's order
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
Outputs
countnumber- How many work logs it has
issue_keytext- The issue
total_secondsnumber- All the time logged, in seconds
worklogslist- The work logged on it
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Time spent
time_spenttextRequired - How long, in Jira's words, such as 30m, 1h 30m or 2d.
- Started
starteddate and time - When the work started. Leave blank for now.
- Comment
commenttext - What was done.
Outputs
authortext- Who logged it
author_usernametext- Their username
commenttext- What was done
createdtext- When it was logged
idtext- The work log's id
issue_keytext- The issue it's on
startedtext- When the work started
time_spenttext- The time, in Jira's words, such as 1h 30m
time_spent_secondsnumber- The time in seconds
Example output
{
"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
sprinttextRequired - The sprint, by its id. Pick a board first to choose from its sprints.
- Issues
issueslistRequired - The keys of the issues to move, such as PROJ-123.
- Board
boardtext - The sprint's board, to pick the sprint from a list.
Outputs
countnumber- How many were moved
issueslist- The keys of the issues moved
sprint_idnumber- The sprint
Example output
{
"count": 1,
"issues": [
"WEB-42"
],
"sprint_id": 37
}Remove watcher
Remove someone from an issue's watchers.
Inputs
- Issue
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- User
usertextRequired - The person, by username, or me for the connected user.
Outputs
issue_keytext- The issue
usertext- The username added or removed
watch_countnumber- How many people watch it now
watcherslist- The usernames watching it now
Example output
{
"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
jqltextRequired - The search, such as project = PROJ AND status = "In Progress" ORDER BY updated DESC.
- How many
max_resultsnumber - The most to return, up to 100. Defaults to 25.From 1 to 100.
- Start at
start_atnumber - How many results to skip, for the next page. Defaults to 0.At least 0.
Outputs
countnumber- How many are listed here
issueslist- The issues found, in the search's order
start_atnumber- Where in the results this page starts, from 0
totalnumber- How many match in all
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Transition
transitiontextRequired - The move to make: pick one, or type its name or the status it leads to.
- Comment
commenttext - A comment to add as it moves.
- Resolution
resolutiontext - A resolution such as Done or Won't Do, when the move's screen asks for one.
Outputs
assigneetext- Who it's assigned to; empty if nobody
assignee_usernametext- The assignee's username; empty if nobody
componentslist- The names of its components
createdtext- When it was created
descriptiontext- Its description
due_datetext- Its due date (YYYY-MM-DD); empty if none
fix_versionslist- The names of the versions it's fixed in
idtext- The issue's id
issue_typetext- Its type, such as Task or Bug
keytext- The issue's key, such as PROJ-123
labelslist- Its labels
linktext- A link to it in Jira
parent_keytext- Its parent's key, for a subtask; empty otherwise
prioritytext- Its priority; empty if none
projecttext- The name of the project it's in
project_keytext- The key of the project it's in
reportertext- Who reported it
reporter_usernametext- The reporter's username
resolutiontext- How it was resolved, such as Done; empty if unresolved
resolvedtext- When it was resolved; empty if unresolved
statustext- Its status, such as To Do or In Progress
status_categorytext- Its status's category: To Do, In Progress or Done
summarytext- Its one-line summary
transitiontext- The transition made
updatedtext- When it last changed
Example output
{
"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
issuetextRequired - The issue's key, such as PROJ-123, or its link.
- Summary
summarytext - A new one-line summary.
- Description
descriptiontext - A new description, replacing the old one.
- Priority
prioritytext - How urgent it is.
- Labels
labelslist - Labels to replace its labels with, each one word.
- Due date
due_datedate - When it's due.
- Components
componentslist - Components to replace its components with, by name or id.
- Fix versions
fix_versionslist - Versions to replace its fix versions with, by name or id.
- Other fields
other_fieldsobject - Any other fields by their id, such as customfield_10010: 5. A select field takes {"value": "Option"}.
Outputs
assigneetext- Who it's assigned to; empty if nobody
assignee_usernametext- The assignee's username; empty if nobody
componentslist- The names of its components
createdtext- When it was created
descriptiontext- Its description
due_datetext- Its due date (YYYY-MM-DD); empty if none
fix_versionslist- The names of the versions it's fixed in
idtext- The issue's id
issue_typetext- Its type, such as Task or Bug
keytext- The issue's key, such as PROJ-123
labelslist- Its labels
linktext- A link to it in Jira
parent_keytext- Its parent's key, for a subtask; empty otherwise
prioritytext- Its priority; empty if none
projecttext- The name of the project it's in
project_keytext- The key of the project it's in
reportertext- Who reported it
reporter_usernametext- The reporter's username
resolutiontext- How it was resolved, such as Done; empty if unresolved
resolvedtext- When it was resolved; empty if unresolved
statustext- Its status, such as To Do or In Progress
status_categorytext- Its status's category: To Do, In Progress or Done
summarytext- Its one-line summary
updatedtext- When it last changed
Example output
{
"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
versiontextRequired - The version, by its id.
- Project
projecttext - The project the version is in, to pick the version from a list.
- Name
nametext - A new name.
- Description
descriptiontext - A new description.
- Release date
release_datedate - When it is or was released.
- Released
releasedtrue/false - Turn on to release it, off to unrelease it.
- Archived
archivedtrue/false - Turn on to archive it, off to restore it.
Outputs
archivedtrue/false- Whether it's archived
descriptiontext- Its description
idtext- The version's id
nametext- Its name, such as 2.4
overduetrue/false- Whether its release date has passed unreleased
project_idtext- The id of its project
release_datetext- Its release date (YYYY-MM-DD); empty if none
releasedtrue/false- Whether it's released
Example output
{
"archived": false,
"description": "Contact form fixes",
"id": "10210",
"name": "2.4",
"overdue": false,
"project_id": "10000",
"release_date": "2026-11-30",
"released": true
}