> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/adding-editing-a-mail-handler/email-this-issue-for-jira-cloud-mail-handler-actions/updating-an-issue.md).

# Updating an issue

The **Update issue** action can be used for updating (setting field values to) an existing issue. Currently, it has no parameters. By default, it does nothing. Add **Set field value** actions under this action to update multiple fields in a single step. For more information, see [Setting field values](/email-this-issue/adding-editing-a-mail-handler/email-this-issue-for-jira-cloud-mail-handler-actions/setting-field-values.md).

![](/files/-MlUZNdNVlNnPhczOIXr)

## **Suppressing Jira's built-in notifications**

By default, Jira sends a notification about every issue update. This notification can be suppressed by enabling this option. Please note that to use this option, **Administer Jira** or **Administer Project** permissions are required.

If you try to suppress Jira's built-in notification while updating an issue and you do not have the required permissions, you get an exception saying "To discard the user notification either admin or project admin permissions are required". If you see this error message in the incoming log, disable the suppress feature, and grant permission to the user or use fallback to a default reporter who has the required permission.

## Limitations

{% hint style="info" %}
**Note**: Due to Jira's permission handling, a customer cannot update a request even if the reporter is the customer itself. As a solution for this, a default reporter must be set as a fallback option, so the action can be performed in case of missing permissions.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meta-inf.hu/email-this-issue/adding-editing-a-mail-handler/email-this-issue-for-jira-cloud-mail-handler-actions/updating-an-issue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.