> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/integrations/other-integrations/productivity/zapier/updating-a-jira-issue.md).

# Updating a Jira issue

This automation keeps Jira synced with AB Tasty by updating issues whenever campaign status changes.

The Zap uses the **AB Tasty Campaign ID** as a unique identifier, stored in a Jira custom field to match campaigns with issues.

### Prerequisites

Before creating the Zap, set up a Jira custom field:

* **Field name:** AB Tasty Campaign ID
* **Field type:** Text Field (single line)
* **Screens:** Add to relevant issue screens

{% hint style="warning" %}
This field must contain the AB Tasty Campaign ID for every issue you want to update automatically.
{% endhint %}

### Zap structure

This Zap includes four steps:

1. Detect campaign status change in AB Tasty
2. Format status to match Jira workflow values
3. Find the related Jira issue using the Campaign ID
4. Update the Jira issue status

### Step-by-step configuration

{% stepper %}
{% step %}

#### **Set up the trigger**

**Configuration:**

* App: AB Tasty
* Trigger event: Campaign Status Change
* Account: Your AB Tasty account

**Key outputs:**

* Campaign ID
* Campaign name
* Campaign status
* Environment
  {% endstep %}

{% step %}

#### Format the status

* **Purpose:** Normalize the AB Tasty campaign status to match your Jira workflow

**Example mapping:**

* `Live` → In Progress
* `Paused`→ On Hold
* `Draft` → To Do

**Configuration:**

* App: Formatter by Zapier 
* Action: Utilities → Lookup Table
* Input: Campaign status
  {% endstep %}

{% step %}

#### Find the Jira issue

* App: Jira Software
* Action: Find Issue

**Configuration:**

* Search field: AB Tasty Campaign ID
* Search value: Campaign ID (from Step 1)

**Output:**

* Jira Issue Key
  {% endstep %}

{% step %}

#### Update the issue

* App: Jira Software
* Action: Update Issue

**Configuration:**

* Issue Key: from Step 3
* Status: formatted value from Step 2

**Optional:**

* Comment: “Campaign {campaign name} is now {status}”
* Description or custom field updates
  {% endstep %}
  {% endstepper %}

### Best practices

* Create Jira issues using the Campaign Created trigger
* Always store the Campaign ID when creating the issue
* Use the Campaign Status Change trigger to update the issue only


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/integrations/other-integrations/productivity/zapier/updating-a-jira-issue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.