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

This field must contain the AB Tasty Campaign ID for every issue you want to update automatically.

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

1

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

2

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

3

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

4

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

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