1-Build Objects/Attributes
Once you complete Source and Destination configurations, it is time to create Object Types and their relations according to the Salesforce data model.
You may also choose to enable or disable Object Schema sharing.
Pro Tip: Commonly, our customers create references from other Object Schemas and are in need of accessing the Salesforce data. We recommend enabling the Object Schema sharing.
Review the options and click the Build Objects/Attributes button.
 |
This needs to be done only one time. When this build is completed successfully you don't need to do it again. You will get a message if you already completed this step.
You may check your new Object Schema now and make sure the Object Types and Attributes are successfully created.
 |
2- Test and Full Imports
You can test the configuration by clicking the Test Import button. This will import the first 100 Salesforce records to your Object Schema. This way, you will have the chance to validate that:
Salesforce credentials are correct, and proper permissions are granted
Jira credentials are correct
Object Schema is set without any problems
After clicking the test import button, wait for the process to finish for a few minutes, and then check your Object Schema.
You may click the Check Import Status button to check the import execution status.
 |
If you are happy with the results of the test run, please run a Full Import.
Pro Tips:
You can select which data types you would like to import under the Admin tab. This way you can decrease the amount of data transferred to your Assets.
Please note that if you have a large number of Salesforce records, this import will take time. We suggest testing it outside of the busy hours when JSM Assets is not used heavily.
Avoid clicking Test Import and Full Import buttons consecutively without waiting for the first one to complete. JSM Assets does not support multiple imports to run simultaneously.
3- Schedule
You have three options for the scheduling.
 |
Pro Tip:
We recommend importing manually first by clicking the “Full Import“ button and measuring the import duration. In case a full import takes long time (i.e. more than an hour), or if there are multiple imports scheduled at the same time in your JSM Site, then hourly scheduling may not be the best option. Prefer Daily scheduling in such case which is the most common import schedule among the JSM customers.
Important note regarding daily imports
Daily imports are commonly scheduled for late night hours (00:00-06:00) when there is no heavy load on the system. However, it is also good to know that these times are also used for the JSM/Assets version updates by Atlassian. In case there is a conflict, the import process fails. You would see the error message in your logs. Please check your import flow daily and configure the Notify Me feature under the Admin tab if you want to get notified when there is an error. We highly recommend following the Operational tips provided on the following page: Operations