# Record :: Import Issue from JIRA

## Summary

Updates a ServiceNow record fields with data from a JIRA Issue using an Inbound Field Map set on the Integration Point

## Action Inputs

| Label             | Name               | Type                                       | Mandatory | Description                                                                                                                                                                                                                               |
| ----------------- | ------------------ | ------------------------------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Integration Point | integration\_point | Reference (Reference: Integration Point)   | No        | The Integration Point we are using that holds the desired Inbound Field Map record                                                                                                                                                        |
| Linkage           | linkage            | Reference (Reference: Jira Record Linkage) | No        | The JIRA Linkage record that ties an issue to a SN record.                                                                                                                                                                                |
| Connector         | connector          | Reference (Reference: Jira Connector)      | No        | \[optional] The sys\_id of the connector to use in the process. If this is blank, the linkage record's connector is used. If there is no connector on the linkage record, then we will use the connector on the integration point record. |
| Issue ID          | issue\_id          | String                                     | No        | \[optional] The JIRA issue ID or Key that was are importing. If this is not specified, we will use the issue ID or Issue Key from the Linkage record                                                                                      |
| Execute ASAP      | execute\_asap      | True/False                                 | No        | Whether to run this as an asynchronous business rule when the record gets created or wait for the job to pick it up in relative order on the queue (typically this should be false)                                                       |

## Action Outputs

| Label         | Name           | Type                                       | Mandatory | Description                                                                                 |
| ------------- | -------------- | ------------------------------------------ | --------- | ------------------------------------------------------------------------------------------- |
| Request       | request        | Reference (Reference: Async Request Queue) | No        | The original asynchronous request queue record used to make the request                     |
| Success       | success        | True/False                                 | No        | Whether the communication and response was as expected                                      |
| Log           | log            | String                                     | No        | Scripted log statements of activities that took place during the operation of this activity |
| Retry Request | retry\_request | Reference (Reference: Async Request Queue) | No        | If there were Retries used in the process, the last retry record is returned                |
| Response JSON | response\_json | String                                     | No        | The resulting JSON representation of the JIRA Issue                                         |

## Notes

* This action belongs to the **JIRA Request Queue** category.
* This action includes reference fields that link to other tables in ServiceNow:
  * references the table.
  * references the table.
  * references the table.
* This action returns 5 output(s) that can be used in subsequent flow steps.

## Example Usage

### Example 1: Basic Usage

This example demonstrates how to use the action with typical inputs.

**Input:**

**Output:**

In this example, the action processes the provided inputs and returns the appropriate outputs. The actual values returned will depend on the specific functionality of this action and the input values provided.


---

# Agent Instructions: 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:

```
GET https://docs.yansalabs.com/jira-integration-framework/technical-docs/spoke-actions/record-import-issue-from-jira.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.