---
title: "Create a Jira issue from Salesforce with Jira Issues (NextGen)"
canonical: "https://support.appfire.com/space/477986818/2560557933/Create%20a%20Jira%20issue%20from%20Salesforce%20with%20Jira%20Issues%20(NextGen)"
format: markdown
---
This page guides you on how to create a Jira issue from a Salesforce record. By creating a Jira issue from Salesforce, you can easily communicate with teams in Jira by bringing the same information from the Salesforce record to a Jira issue. For example, when a Salesforce agent needs to escalate a Case to the development team in Jira, they can create the Jira issue from inside the Case and: Set the Jira issue priority to  High  to match the Case's priority. Set the Jira issue component to  UI , matching the Case Reason  Installation . Review the information being sent to Jira, prior to creating the Jira issue. Before you start Your administrator has completed a  project binding  as well as  entity and field mappings  in Jira. Your administrator has  configured the Visualforce pages  required for the object. Create a Jira issue In a Salesforce record, click  Associate/Create . The  Associate Or Create Jira Issue  window appears.      Click  Create Jira Issue  and the  Create Jira Issue  pop-up window appears.   Choose the desired  Jira Project  and  Issue Type . All field and value mappings set by your administrator will be used to create the Jira issue. If you select  Sub-task  as the  Issue Type , a required  Parent  field appears directly below it. Search for and select the Jira issue that should be the Sub-task's parent (search for issues with at least 3 characters). You can't create the Sub-task until a parent is selected. You can choose to toggle the following options: View Only : Manual and automatic synchronization is disabled. Auto Pull : Changes to the associated Jira issue are pulled automatically into this record. Auto Push : Changes to this record are pushed automatically to associated Jira issues, provided the required triggers are installed. Some combinations are not possible and cannot be selected. Refer to the help provided under the  What Will Happen?  panel. You can also choose what to do after the Jira issue is created by choosing from the following options: Do nothing Pull from Jira   Add, edit, or delete the values if you need. See  Notes on Supported Fields  for more information. Upon successful creation, an  Issue created successfully  message is shown. Tiles view Table view   Notes on supported fields The  Review & Create  window performs the following actions: It renders fields that appear in the original  Create Issue  dialog in Jira, respective to the project and issue type selected. Shows all fields regardless of whether they are mapped or not. Automatically populates the field value. If the populated value is not mapped and the default value is set to  Raise error , you can still create a new issue in Jira. However, it won't allow you to synchronize it with Connector for Salesforce and Jira. Value mappings and default values are set by your administrator. Ensure that the correct mappings are in place to prevent synchronization issues. The following field types are rendered in the  Review & Create  window: Text fields like  Summary Rich text fields like  Description  (If enabled in  connection settings , Jira multiline fields will use rich text fields; otherwise, plain text formatting will be applied.) Request type (only for JSM) Priority Components Versions Labels Numbers Select lists Checkboxes Radio buttons Date Date Time The following fields are rendered in this order (after which, any other fields would be rendered in no specific order): summary description priority components versions fixVersions labels epic name sprint Related information Configure an association Automate your integration Associate a Jira Issue from Salesforce with Jira Issues  (NextGen)