# Issue Updated

> Windows | Cross-platform

## Project compatibility

Windows | Cross-platform

## Overview

The Issue Updated trigger starts a workflow when an existing Jira issue is updated in the specified project and issue type. It uses polling to detect changes, supports optional field-level filters (for example, status, labels, assignee), and supplies a hydrated issue object in the output, suitable for downstream automations. All permissions and pagination rules for the Jira Cloud REST API are enforced.

| Description | API Method | API Path | Scopes |
| --- | --- | --- | --- |
| List issues for polling updates | GET | `/rest/api/2/search` | `read:jira-work` Required so the connector can call `GET /rest/api/2/search` |

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Project | Jira project key to monitor for updated issues (for example, `ABC`) | string |
| Issue type | Issue type to monitor for updates (for example, Story, Task, Bug, Epic) | string |
| Data filter | Optional data filter on issue fields (dynamic fields like status, priority, labels, assignee, date fields) used to restrict which new issues actually trigger the workflow. | variable |

## Output

| Parameter | Description | Data Type |
| --- | --- | --- |
| Issue | Full issue object for the updated issue, including all standard and custom fields | object |
| Issue ID | Unique ID of the updated issue | string |
| Issue key | Key of the updated issue (for example, `ABC-123`) | string |

:::note
* In API workflows, a single response object is returned as the output. Any required fields can be extracted directly from this object.
* In RPA workflows, some output parameters may differ, but the necessary values can still be retrieved from the response object even if they are not explicitly exposed.
:::