---
title: "Automation Action: Jira"
description: "New automation action Jira"
url: https://help.stackby.com/es/articles/455-automation-action-jira
collection: "Stackby Automations"
updated: 2026-06-23
language: es
alternates: [en]
---

# Automation Action: Jira

New automation action Jira

## **How to Use Stackby’s New Jira Automation Actions**

Stackby recently introduced powerful **Jira automation actions** that let you automate creating and updating Jira issues directly from your Stackby workspace — no coding required. 

With these new actions, you can:

-   **Create a new Jira Issue** using the _“Create Issue”_ action
    
-   **Update an existing Jira Issue** using the _“Update Issue”_ action
    

![](https://staticfiles.gleap.io/ghelparticle/CFtEzYDy5qYLON3IBWhDaD6rOX1MpBksk1so4u0gs4rEDYPiYhpKmHNsngX0aJWFniAivS2ZZ59.png)

In this article, we'll learn — from connecting your Jira account to setting up each automation.

### **Step 1 — Connect Your Jira Account**

Before you can automate anything, you need to connect Stackby to your Jira Cloud instance.

1.  **Open your Stack** where you want to automate tasks.
    
2.  Go to **Automations** from the top toolbar.
    
3.  Click **\+ Create New Automation**.
    
4.  Choose a Trigger — this tells Stackby _when_ to run the automation (e.g., when a new record is added to a view, when a record is updated, etc.) 
    
5.  After selecting the trigger and testing it, add a new action.
    
6.  Choose your **Jira automation action** (either _Create Issue_ or _Update Issue_).
    
7.  When prompted, **select or connect your Jira account**.
    
    -   You may need to login with your Atlassian credentials and grant permissions.
        
    -   Once connected, Stackby will be able to read your Jira projects, site, and issue types.
        

### **Step 2 — Automate Creating a New Jira Issue**

Here’s how you set up the **Create Issue** action:

### **Configuration Steps**

1.  After connecting your Jira account, you’ll see fields like:
    
    -   **Site** – your Jira Cloud domain
        
    -   **Project** – which Jira project to create the issue in
        
    -   **Issue Type** – e.g., Bug, Task, Story, etc.
        
        ![](https://staticfiles.gleap.io/gattachments/0efxbH51n7OBhtSAGz0Znn9EAHCDtCN2QixGSGdbVVabmj1Cg7mEmRSE8uFGiTYuvfVIVK9VIKz.png)
        
2.  Select the appropriate values that match your workflow.
    
3.  **Map issue details** from your Stackby record to the Jira issue:
    

-   **Summary** — the issue title
    
-   **Description** — longer details about the task/bug
    
-   **Reporter** — who created it (if your Jira permissions allow)
    
-   **Assignee** — who should be assigned
    
-   **Status -** status of the ticket (QA test PROD, to do)
    
-   **Labels** — tags to categorize the issue
    

4.  **Other fields** — custom fields depending on your Jira issue configuration
    

![](https://staticfiles.gleap.io/gattachments/2n0tsolWGXToiy7cVPQDkmEe6cVYCSS3hdyWkfAFJt1XZ3gkjOuoU0zNVO0tEf4Hgb75U79Ub8z.png)

5.  After configuring all the fields, **test the action** to make sure Stackby can successfully create a Jira issue.
    
6.  Once the test passes, **save and turn on the automation**.
    

Now Stackby will automatically create new Jira issues when your trigger condition is met.

### **Step 3 — Automate Updating an Existing Jira Issue**

Now let’s look at updating issues you already have.

### **Configuration Steps**

1.  **Add a new action** after your trigger in the automation editor.
    
2.  Choose **“Update Issue”**.
    
3.  Select your Jira account again (if needed).
    
4.  Choose the **Jira Site** and **Project** where the issue exists.  
    
    ![](https://staticfiles.gleap.io/gattachments/uBcYZ1RjhqFZ1MzhPkEPOJSNaU3s4kA1Uld9spJfRiW4VGOQXVIFJCTVMhYhQIB3JYlouknSjgE.png)
    
5.  Now you’ll be asked to provide:  
    **Issue Key or Issue ID** — Use the field you may have saved earlier from a _Create Issue_ step, or enter it manually.
    
    ![](https://staticfiles.gleap.io/gattachments/yBZyjzhI8ZsYlih033jf16iuv8MMERxvTGYsHzhCGmjveqxmLApRVNNV4XG108Wqe1JcG9p1THi.png)
    
6.  Pick which fields in Jira you want to update:
    
    -   **Summary**
        
    -   **Description**
        
    -   **Status**
        
    -   **Assignee**
        
    -   **Priority**
        
    -   **Any custom field**
        
        ![](https://staticfiles.gleap.io/gattachments/cNGuLAndgUd1thPxRPjv7LFvp81PaayrFTu0qr3WFV01pUVi8ZKiBYuizrl2kHfRBWzumn853JF.png)
        
    -   You can leave a field blank if you want it cleared in Jira — so map carefully.  
        
7.  **Test the action** to make sure your update works properly.
    
8.  Save and **enable the automation**.  
    

Once live, any changes in Stackby that meet your trigger condition will update the corresponding Jira issue automatically.

## **FAQ**

### **1\. Can I create issues in multiple Jira projects?**

Yes. You can:

-   Create separate automations for different Jira projects, or
    
-   Dynamically select projects if Stackby supports field-based mapping for the Project field.
    

Each automation action can point to **one Jira project at a time**.

### **2\. Can I update the status of a Jira issue using Stackby?**

Yes, as long as:

-   The **Status** field is available for the selected issue type, and
    
-   The status transition is allowed in Jira’s workflow.
    

If a status change fails, it’s usually due to Jira workflow restrictions.

### **3\. What happens if the Issue ID or Issue Key is missing?**

For the **Update Issue** action:

-   The automation will fail if no valid **Issue Key or Issue ID** is provided.
    
-   Best practice is to **store the Issue Key** returned from the _Create Issue_ action in a Stackby column and reuse it later.
    

### **4\. Are custom Jira fields supported?**

Yes. Stackby supports **custom Jira fields**, provided:

-   They are available for the selected project and issue type
    
-   Your Jira user has permission to view and edit them
    

Custom fields will appear automatically in the action setup when supported.