Skip to content
Nappai Documentation

Jira Issue Handler

Jira Issue Handler lets you manage Jira tickets directly from your Nappai dashboard. With a few clicks you can create new issues, update existing ones, add subtasks, or delete tickets. It works with any Jira Cloud project you have access to and supports batch processing through Mapping Mode.

How it Works

When you add the component to a workflow, it connects to your Jira Cloud instance using the credentials you set up in Nappai. The component sends HTTP requests to Jira’s REST API to perform the chosen operation. If you enable Mapping Mode, the component can take a list of records from a previous step and create or update many issues in one go, using the mapping options (Fixed, Mapped, or Javascript) to supply the data for each field.

Operations

This component offers several operations that you can select based on what you need to do. You can only use one operation at a time:

  • Create Issue: Create a new Jira issue in the selected project.
  • Update Issue: Modify an existing Jira issue’s fields.
  • Create Subtask: Add a new subtask under a parent issue.
  • Update Subtask: Edit an existing subtask’s details.
  • Delete Issue / Subtask: Remove an issue or subtask from Jira.

To use the component, first select the operation you need in the “Operation” field.

Inputs

Mapping Mode

This component has a special mode called “Mapping Mode”. When you enable this mode using the toggle switch, an additional input called “Mapping Data” is activated, and each input field offers you three different ways to provide data:

  • Fixed: You type the value directly into the field.
  • Mapped: You connect the output of another component to use its result as the value.
  • Javascript: You write Javascript code to dynamically calculate the value.

This flexibility allows you to create more dynamic and connected workflows.

Credential

Select the Jira API credential you have configured in Nappai.

  1. Go to the Credentials section of Nappai and create a new Jira API credential.
  2. In the component, choose that credential from the Credential dropdown.

Input Fields

The following fields are available to configure this component. Each field may be visible in different operations:

  • Operation: Choose the action you want to perform.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

  • Credential: Select the Jira API credential you created.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

  • Tool Name: The name of the tool that will be used when this component is connected as a tool.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

  • Tool Description: A detailed description of what this tool does.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

  • Tools arguments metadata: Defines the arguments metadata for the tools.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

  • Mapping Mode: Enable mapping mode to process multiple data records in batch.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

  • Mode: Choose between a simplified setup with default options or full control with advanced settings.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask

  • Project Key: Select the Jira project where the operation will be performed.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask

  • Issue Type: Type of issue, e.g., Task, Bug, Subtask.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask

  • Priority: Priority level of the issue (Low, Medium, High, etc.).

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask

  • Issue Summary: The main title or summary of the issue.

    • Visible in: Create Issue, Create Subtask, Update Issue, Update Subtask

  • Description: Detailed description of the issue.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask

  • Assignee Account ID: User account ID to assign the issue to.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask

  • Issue Key: Unique key of the issue to be modified.

    • Visible in: Update Issue, Update Subtask, Delete Issue / Subtask

  • Issue Parent Key: Unique Key of the Issue that will act as parent of the current Subtask being created.

    • Visible in: Create Subtask, Update Subtask

  • Issue Status: Current status of the issue (To Do, In Progress, Done, etc.).

    • Visible in: Update Issue, Update Subtask

  • Comment: Optional comment to add to the issue.

    • Visible in: Update Issue, Update Subtask

  • Tools arguments metadata: Defines the arguments metadata for the tools.

    • Visible in: Create Issue, Update Issue, Create Subtask, Update Subtask, Delete Issue / Subtask

Outputs

  • Jira Response: The raw response from Jira’s API. This can be used to check the status of the operation or to pass data to later steps.
  • Tool: A tool object that can be used by Nappai’s AI agents to call this component programmatically.

Usage Example

Scenario: You want to create a new bug in the “Support” project and assign it to a specific user.

  1. Drag the Jira Issue Handler into your workflow.
  2. Set Operation to Create Issue.
  3. Choose the Credential you created earlier.
  4. In Project Key, select SUPPORT.
  5. Set Issue Type to Bug.
  6. Enter a short Issue Summary like “Login page error”.
  7. Provide a detailed Description of the problem.
  8. Set Priority to High.
  9. Enter the Assignee Account ID of the developer who will fix it.
  10. Run the workflow. The component will create the issue and return the Jira response.

Batch Example: If you have a list of error logs, enable Mapping Mode, connect the list to Mapping Data, and map each field (summary, description, etc.) to the corresponding columns. The component will create a separate issue for each log entry.

  • Jira Base Issue Handler – The underlying component that provides common Jira issue functionality.
  • Jira Issue Search – Find issues based on filters before deciding to update or delete them.
  • Jira Comment Handler – Add or edit comments on existing issues.

Tips and Best Practices

  • Use Mapping Mode when you need to process many issues at once; it saves time and reduces API calls.
  • Test a single issue first to confirm your credentials and field values are correct before running a batch.
  • Keep your Jira API token secure; never share it in public workflows.
  • When deleting issues, double‑check the Issue Key to avoid accidental data loss.
  • Use the Tool output if you want an AI agent to trigger this component automatically.

Security Considerations

  • Store your Jira API token in Nappai’s secure credential store.
  • Limit the permissions of the Jira user to only the projects and actions needed.
  • Review the Jira API response for any error messages and handle them gracefully in your workflow.