Important Note: In order to create a flow, you will use integrator.io. If you do not have a subscription to integrator.io, you may request a 30-day free trial by logging into your integrator.io account, going to My Account https://integrator.io/
All pre-existing Project records in NetSuite and JIRA must be cross-referenced before enabling the Connector in Production to avoid the risk of duplicate records being created. All updates made on pre-existing records in NetSuite are synced over to the appropriate Projects in JIRA.
- Establish a JIRA Connection or use an existing one.
- Set Relative URI to /rest/api/2/project
- Set HTTP Method to GET
- Set Export Type to ALL
- Click Next when complete.
The Lookup criteria is used to find a match between JIRA Projects and NetSuite Projects. You can choose and use Lookup criteria that best suits the data in NetSuite and JIRA. In the above example, we have assumed that all Projects in NetSuite and JIRA have the same name. The idea here is to find a field or common ground that has the identical and unique value between the two systems, and use them to populate the ID information on NetSuite records.
Click Next to continue.
Click Launch Mapper and set the field mapping (below). This field mapping indicates the the 'ID' value from JIRA Project will be written to the the 'JIRA Project ID' field on the NetSuite Project record.
Click Save & Close on the Field Mapper, then Next to continue.
Set the Name as desired and Save the flow.
This is a batch flow with the ability to UPDATE the JIRA Project ID field on the NetSuite record. Be sure to click the play button against the flow to execute. The status of the flow can be tracked on the Dashboard.
Note: A similar custom flow can be created (for one-time use only) to map the IDs between Employee records in NetSuite and Users in JIRA. The record type in this case should be Employee, the Lookup criteria would be Email and Mappings should be name (in JIRA) mapped to JIRA User Key (on NetSuite Employee record).