Configure and run flows in the Jira Cloud platform – NetSuite Quickstart integration template

Contents

• Overview: Understanding the Jira Cloud platform – NetSuite integration template
• Install the Jira Cloud platform – NetSuite integration template
•  Configure and run flows in the Jira Cloud platform – NetSuite integration template
  • Jira Cloud platform issues to NetSuite cases
  • Jira Cloud platform issues to NetSuite issues
  • Jira Cloud platform issues of type task to NetSuite project tasks
  • Jira Cloud platform users to NetSuite customers
  • Jira Cloud platform projects to NetSuite (custom record - Jira projects)
  • Jira Cloud platform time tracking to NetSuite time tracking
  • NetSuite issues to Jira Cloud platform issues
  • NetSuite cases to Jira Cloud platform issues
  • NetSuite case details to Jira Cloud platform issues comments
  • NetSuite case assignments to Jira Cloud platform issue assignees
  • NetSuite customers to Jira Cloud platform users
  • NetSuite employees to Jira Cloud platform users
  • NetSuite projects to Jira Cloud platform projects
  • NetSuite project tasks to Jira Cloud platform issues
  • NetSuite case attachments to Jira Cloud platform issue attachments
  • NetSuite customers to Jira Cloud platform custom field options
  • NetSuite issue products to Jira Cloud platform custom field options

After you install the template, additional record mapping is required to integrate the template’s exports and imports with your Jira Cloud platform and NetSuite apps.

Note that all your flows are disabled when first installed. After configuring the flows, you can enable them in your Flows dashboard or in Flow Builder with the Off/On toggle button. Then run or schedule each flow.

Jira Cloud platform issues to NetSuite cases

This flow syncs Jira Cloud platform issues as NetSuite cases. This flow creates cases in NetSuite only when a matching case is not found. When a matching case is found, this flow updates the cases in NetSuite.

Flow details

• Export source: Jira Cloud platform
• Built-in Listener: Get Jira Cloud platform issues - get all issues from Jira Cloud platform.
• Import destination: NetSuite
• Built-in Import: Import NetSuite cases - add/update cases into NetSuite with the configured custom field as lookup identifier.
• Built-in Import: Import NetSuite cases(for Message) - update cases into NetSuite with the configured custom field as lookup identifier.
• Built-in import: Import Jira Cloud platform issues – store NetSuite case ID in Jira Cloud platform issues.

Before you begin

1. Employees in NetSuite should be the same as Users in the Jira Cloud platform.
   1. Jira Cloud platform user ID should be stored in the custom field of NetSuite employees.
2. Customers in NetSuite should be the same as Users in the Jira Cloud platform.
   1. Jira Cloud platform user ID should be stored in the custom field of NetSuite customers.
3. Type in NetSuite should be the same as the Issue type in Jira Cloud platform.
4. Projects in NetSuite should be the same as Projects in Jira Cloud platform.
   1. Jira Cloud platform project ID should be stored in the custom field of NetSuite projects.
5. Create a custom field of type text on issues in Jira Cloud platform to store the Internal ID of NetSuite cases.

Setup instructions

1. Create a webhook for Get Jira Cloud platform issues.
2. Configure static mapping for Status (InternalId), Priority (InternalId) in Import NetSuite cases.
3. Configure dynamic mapping for Profile (InternalId) in Import NetSuite cases.

Jira Cloud platform issues to NetSuite issues

This flow syncs the Jira Cloud platform issues as NetSuite issues. This flow creates issues in NetSuite only when a matching issue is not found. When a matching issue is found, this flow updates the issue.

Flow details

• Export source: Jira Cloud platform
• Built-in Listener: Get Jira Cloud platform issues - get all issues from Jira Cloud platform.
• Import destination: NetSuite
• Built-in Import: Import NetSuite issues - add/update issues into NetSuite with the configured custom field as lookup identifier.
• Built-in Import: Import Jira Cloud platform issues - store NetSuite issue ID in Jira Cloud platform issues.

Before you begin

1. NetSuite Employees should be the same as Jira Cloud platform Users.
   1. Jira Cloud platform user ID should be stored in the custom field of NetSuite employees.
2. Projects in NetSuite should be the same as Projects in Jira Cloud platform. 
   1. Jira Cloud platform project ID should be stored in the custom field of NetSuite projects.
3. Create a custom field of type text on issues in Jira Cloud platform to store Internal ID and generate the product item of NetSuite cases.

Setup instructions

1. Create a webhook for Get Jira Cloud platform issues.
2. Configure static mapping for Issue Status (Name) and Priority (Name) in Import NetSuite issues.

Jira Cloud platform issues of type task to NetSuite project tasks

This flow syncs Jira Cloud platform issues of type tasks as NetSuite project tasks. This flow creates project tasks in NetSuite only when a matching project task is not found. When a matching project task is found, this flow updates the project tasks.

Flow details

• Export source: Jira Cloud platform
• Built-in Listener: Get Jira Cloud platform issues - get all issues from Jira Cloud platform.
• Import destination: NetSuite
• Built-in Import: Import NetSuite project tasks - add/update project tasks into NetSuite with the custom field as the lookup identifier.
• Built-in Import: Import Jira Cloud platform issues - store NetSuite project task internal id in Jira Cloud platform issues.

Before you begin

1. Projects in NetSuite and projects in Jira Cloud platform should be the same.
   1. Jira Cloud platform project ID should be stored in NetSuite projects custom field.
2. Create a custom field of type text on issues (type task) in Jira Cloud platform to store Internal ID of NetSuite project tasks.

Setup instructions

1. Create a webhook for Get Jira Cloud platform issues.
2. Configure dynamic mapping for Project Name (InternalId) in Import NetSuite project tasks.
3. Configure static map for Status (InternalId) in Import NetSuite project tasks.

Jira Cloud platform users to NetSuite customers

This flow syncs the Jira Cloud platform users to NetSuite customers. This flow creates customers in NetSuite only when a matching customer is not found. When a matching customer is found, this flow updates the customers.

Flow details

• Export source: Jira Cloud platform
• Built-in Listener: Get Jira Cloud platform users - get all users from Jira Cloud platform.
• Import destination: NetSuite
• Built-in Import: Import NetSuite customers - add/update customers into NetSuite with custom field as the lookup identifier.

Setup instructions

1. Create a webhook for Get Jira Cloud platform users.
2. Add Subsidiary mapping in Import NetSuite customers.

Jira Cloud platform time tracking to NetSuite time tracking

This flow syncs time logged in a Jira Cloud platform time-tracking record with NetSuite. This flow can be configured to sync time-tracking information to a NetSuite Issue, Case, or Project Task.

Note: Time-tracking information for Jira Cloud platform issue types task, bug, and story can be synced as NetSuite project task, NetSuite issue, and NetSuite case respectively. Other Jira Cloud platform issue types are not supported.

Flow details

• Export source: Jira Cloud platform
• Built-in Listener: Get Jira Cloud platform time tracking - get all time tracking from Jira Cloud platform.
• Import destination: NetSuite
• Built-in lookup: Get Jira Cloud platform issues - get all the issues from Jira Cloud platform by issue ID.
• Built-in Import: Import NetSuite time tracking - add/update time tracking into NetSuite with configured custom field as the lookup identifier.
  • preMapFunction hook: Processing NetSuite time tracking.js - normalize data for issue types.

Before you begin

1. NetSuite issue, case, project task, the project must be in sync with corresponding Jira Cloud platform records.
2. Create custom fields of type Select List (single choice) on issues in Jira Cloud platform to store Location, Billable, Service item of NetSuite.

Setup instructions

1. Create a webhook for Get Jira Cloud platform time tracking.
2. Make the appropriate changes in the script for issue type story according to your requirements.

Jira Cloud platform projects to NetSuite (custom record - Jira projects)

This flow syncs the Jira Cloud platform projects as NetSuite Jira projects (custom record). This flow creates Jira Cloud platform projects in NetSuite only when a matching Jira project (custom record) is not found. If a matching Jira project is found, the flow updates the NetSuite Jira projects (custom record).

Flow details

• Export source: Jira Cloud platform
• Built-in export: Get Jira Cloud platform projects - get all projects from Jira Cloud platform.
• Import destination: NetSuite
• Built-in Import: Import NetSuite (custom record - Jira projects) - add/update Jira projects (custom record) with project ID as the lookup identifier.

NetSuite issues to Jira Cloud platform issues

This flow syncs the NetSuite issues as Jira Cloud platform issues. This flow creates issues in Jira Cloud platform only when a matching issue is not found. When a matching issue is found, this flow updates the issues.

Flow details

• Export source: NetSuite
• Built-in listener: Get NetSuite issues - get all issues from NetSuite.
• Import destination: Jira Cloud platform
• Built-in lookup: Get NetSuite (custom record - Jira project) - get a Jira project (custom record) from NetSuite by ID.
• Built-in lookup: Get NetSuite employees - get all employees from NetSuite by ID.
• Built-in import: Import Jira Cloud platform issues - add/update issues into Jira Cloud platform with ID as the lookup identifier.
• Built-in import: Import NetSuite issues - update issues into NetSuite by internal ID.
• Built-in import: Import Jira Cloud platform comments - add comments into Jira Cloud platform by Issue ID.

Before you begin

1. Employees in NetSuite and users in Jira Cloud platform should be the same.
   1. Jira Cloud platform user ID should be stored in the custom field of NetSuite employees.
2. Projects in NetSuite and Projects in Jira Cloud platform should be the same.
   1. Jira Cloud platform project ID should be stored in the custom field of NetSuite project.
3. Create a custom field of type text on issues in Jira Cloud platform to store internal ID and issue number of NetSuite issues.

Setup instructions

Configure static mapping for fields.priority.name and fields.issuetype.name in Import Jira Cloud platform issues.

NetSuite cases to Jira Cloud platform issues

This flow syncs NetSuite cases as Jira Cloud platform issues. This flow creates issues in Jira Cloud platform only when a matching issue is not found. When a matching issue is found, this flow updates the issues.

Flow details

• Export source: NetSuite
• Built-in listener: Get NetSuite cases - get all cases from NetSuite.
• Import destination: Jira Cloud platform
• Built-in lookup: Get NetSuite (custom record - Jira project) - get a Jira project (custom record) from NetSuite by ID.
• Built-in lookup: Get NetSuite employees - get an employee from NetSuite by ID.
• Built-in import: Import Jira Cloud platform issues - add/update issues into Jira Cloud platform with the configured custom field as lookup identifier.
• Built-in lookup: Get Jira Cloud platform comments - get all comments from Jira Cloud platform by issue ID.
• Built-in import: Import Jira Cloud platform comments - add/ ignore comments into Jira Cloud platform by ID.
• Built-in import: Import NetSuite cases - store Jira Cloud platform issue ID in NetSuite cases.

Before you begin

1. Employees in NetSuite and Users in Jira Cloud platform should be the same.
   1. Jira Cloud platform user ID should be stored in the custom field of NetSuite employees.
2. Customers in NetSuite and Users in Jira Cloud platform should be the same.
   1. Jira Cloud platform user ID should be stored in the custom field of NetSuite customers.
3. Type in NetSuite and Issue type in Jira Cloud platform should be the same.
4. Projects in NetSuite and Projects in Jira Cloud platform should be the same.
   1. Jira Cloud platform project id should be stored in the custom field of NetSuite projects.
5. Create a custom field of type text on issues in Jira Cloud platform to store Internal ID and case Number of NetSuite cases.

Setup instructions

Configure static mapping for fields.priority.name in Import Jira Cloud platform issues (add).

NetSuite case details to Jira Cloud platform issues comments

This flow syncs NetSuite case details as Jira Cloud platform issues comments. When case details are added in NetSuite case details, this integration flow exports the case details from NetSuite to Jira Cloud platform issues comments.

Flow details

• Export source: NetSuite
• Built-in export: Get NetSuite case details - get case comments only with visibility as internal from NetSuite that have been modified since this flow last ran.
• Import destination: Jira Cloud platform
• Built-in lookup: Get Jira Cloud platform comments - get all comments from Jira Cloud platform by issue ID.
• Built-in import: Import Jira Cloud platform comments - add/ignore comments into Jira Cloud platform with ID as the lookup identifier.
  • preMapFunction hook: Processing Jira comments.js - normalize data for comments.

Before you begin

Run the flow NetSuite cases to Jira Cloud platform issues. The Jira Cloud platform issue ID should be stored in the  NetSuite cases custom field.

Setup instructions

Configure mapping for visibility.type and visibility.value in Import Jira Cloud platform comments.

NetSuite case assignments to Jira Cloud platform issue assignees

This integration flow syncs NetSuite case assignments as Jira Cloud platform issue assignees. When case assignments are added to NetSuite case assignments, this integration flow exports the case assignments from NetSuite to Jira Cloud platform issue assignees.

Flow details

• Export source: NetSuite
• Built-in export: Get NetSuite case assignments - get case assignments details from NetSuite that have been modified since this flow last ran.
• Import destination: Jira Cloud platform
• Built-in import: Import Jira Cloud platform issue assignees - update into Jira Cloud platform issue assignees with ID as the lookup identifier.

Before you begin

1. Sync NetSuite cases with Jira Cloud platform issues.
   1. Jira Cloud platform issue ID should be stored in the custom field of NetSuite cases.
2. Employee name in NetSuite and user’s name in Jira Cloud platform should be the same.

NetSuite customers to Jira Cloud platform users

This flow syncs the customers from NetSuite as users in Jira Cloud platform. The flow creates users in Jira Cloud platform only if a matching user is not found. If a matching user is found, the flow ignores the users. Updates are not supported.

Flow details

• Export source: NetSuite
• Built-in listener: Get NetSuite customers – get all customers from NetSuite.
• Import destination: Jira Cloud platform
• Built-in import: Import Jira Cloud platform users – add and ignore user into Jira Cloud platform with accountId as the lookup identifier.
• Built-in import: Import Netsuite customers – update customers into NetSuite with internal ID as the lookup identifier.

NetSuite employees to Jira Cloud platform users

This flow syncs the employees from NetSuite as users in Jira Cloud platform. The flow creates users in Jira Cloud platform if a matching user is not found. If a matching user is found, the flow ignores the users. Updates are not supported.

Flow details

• Export source: NetSuite
• Import destination: Jira Cloud platform
• Built-in listener: Get NetSuite employees – get all employees from NetSuite.
• Built-in import: Import Jira Cloud platform users – add or ignore users into Jira Cloud platform with configured custom field as the lookup identifier.
• Built-in import: Import NetSuite employees – update employees into NetSuite with email as the lookup identifier.

NetSuite projects to Jira Cloud platform projects

This flow syncs the projects from NetSuite as projects in Jira Cloud platform. The flow creates projects in Jira Cloud platform only if a matching project is not found. If a matching project is found, the flow updates the project. 

Flow details

• Export source: NetSuite
• Built-in listener: Get NetSuite projects – get all NetSuite projects.
• Import destination: Jira Cloud platform
• Built-in lookup: Get NetSuite customers by id – get all customers from NetSuite by ID.
• Built-in import: Import Jira Cloud platform projects – add or update projects into Jira Cloud platform with project id as the lookup identifier.
• Built-in import: Import NetSuite projects – update projects into NetSuite with internalid as the lookup identifier.

Before you begin

1. Project type in Jira Cloud platform and Jira Cloud platform project type (custom field) in NetSuite should be the same.
2. Customer in NetSuite and User in Jira Cloud platform should be the same.
   1. Jira Cloud platform user id should be stored in NetSuite customers custom field.

NetSuite project tasks to Jira Cloud platform issues

This flow syncs the project tasks from NetSuite as issues in Jira Cloud platform. The flow creates issues in Jira Cloud platform only if a matching issue is not found. If a matching issue is found, the flow updates the issue.

Flow details

• Listener source: NetSuite
• Built-in listener: Get NetSuite project tasks – get all project tasks from NetSuite.
• Built-in lookup: Get NetSuite projects – get a project from NetSuite with the company.name as the lookup identifier.
• Import destination: Jira Cloud platform
• Built-in import: Import Jira Cloud platform issues – add or update issues of type into Jira Cloud platform with custom field as the lookup identifier.
• Built-in import: Import NetSuite project tasks – update projects tasks into NetSuite with internalid as the lookup identifier.

Before you begin

Projects in NetSuite and Project in Jira Cloud platform should be the same. (Jira Cloud platform project id should be stored in NetSuite projects custom field).

Setup instructions

Configure mapping for fields.issuetype.name in Import Jira Cloud platform issues.

NetSuite case attachments to Jira Cloud platform issue attachments

This flow syncs NetSuite case attachments as Jira Cloud platform issue attachments. When cases with attachments are created in NetSuite, this integration flow exports case attachments from NetSuite to Jira Cloud platform issue attachments.

Flow details

• Export source: NetSuite
• Built-in export: Get NetSuite cases - get all cases from NetSuite that have been created since this flow last ran.
  • preSavePage hook: ProcessCaseFiles.js - removes case files duplicates.
• Import destination: Jira Cloud platform
• Built-in lookup: Get NetSuite messages - get all messages from NetSuite by ID.
• Built-in export transfer: Get NetSuite case attachments - get all case attachments from NetSuite by ID.
• Built-in import transfer: Import Jira Cloud platform issues attachments - add issue attachments to Jira Cloud platform.
  • preResponseMap hook: ProcessMessageAttachment.js - processes message attachments.
• Built-in export transfer: Get NetSuite message attachments - get all message attachments from NetSuite by ID.
• Built-in import transfer: Import Jira Cloud platform issue attachments - add issue attachments to Jira Cloud platform.

Before you begin

JiraNS issue ID in NetSuite and issue ID in Jira Cloud platform should be the same.

Setup instructions

Configure the search parameters for the internal ID (number) value in the NetSuite message record lookup.

NetSuite customers to Jira Cloud platform custom field options

This flow syncs NetSuite customers as Jira Cloud platform custom field options. When customers are added to NetSuite, this integration flow exports customers from NetSuite to Jira Cloud platform custom field options.

Flow details

• Export source: NetSuite
• Built-in export: Get NetSuite customers - get all customers from NetSuite that have been modified since this flow last ran.
• Import destination: Jira Cloud platform
• Built-in Import: Import Jira Cloud platform custom field options - add custom field options into Jira Cloud platform.

Setup instruction

1. Create a select list (single choice) type custom field on issues in Jira Cloud platform to store NetSuite customers name.
2. Add custom field ID for the Import Jira Cloud platform.

Note: While creating the custom field, you can fetch the custom field ID in the URL.

NetSuite issue products to Jira Cloud platform custom field options

This flow syncs NetSuite issue products as Jira Cloud platform custom field options. When product issues are created in NetSuite, this integration flow exports issue products from NetSuite to Jira Cloud platform custom field options.

Flow details

• Export source: NetSuite
• Built-in export: Get NetSuite issue products - get all issue products from NetSuite that have been modified since this flow last ran.
• Import destination: Jira Cloud platform
• Built-in Import: Import Jira Cloud platform custom field options - add custom field options into Jira Cloud platform. 

Setup instruction

1. Create a select list (single choice) type custom field on issues in Jira Cloud platform to store NetSuite customer's name.
2. Add custom field ID for the Import Jira Cloud platform.