/
Connection Configuration for MultiSource Importer for JSM Assets

Connection Configuration for MultiSource Importer for JSM Assets

  • In production

    • Multiple connections can be created after defining the sources and destinations.

    1. To begin, click the “Add New Connection” button.

    Screenshot 2025-06-30 at 11.59.35.png

    1. Give a name for your connection.

    2. Choose a source from the list.

    3. Select a destination from the provided options.

    4. If this is your first attempt at configuring the import, select “None” from the schedule list. You can modify this value after completing the steps outlined on this page.

    5. Click the “Save” button.

    6. Press the “Close” button to return to the Connections list.

    7. Follow the three steps detailed below:

    Step 1

    To proceed, click the “Build” button. Additionally, you have the option to enable or disable Object Schema sharing based on your preferences.

    Pro Tip: Many of our customers create references from other Object Schemas and need access to data. We recommend enabling the Object Schema Sharing.

    Review the options and click the Build Schema Model button.

    Screenshot 2025-06-30 at 12.04.52.png

    This step only needs to be completed once. Once the build is successful, you won’t need to repeat it. If this step has already been completed, a message will appear confirming it.

     

    Now is a great time to review your Object Schema. Please ensure that the Object Type and Attributes have been created successfully.

    2. Test Import

    You can test the configuration by clicking the Test Import button. This will import the first 10 records into your Object Schema. After the test runs, wait a few minutes for the process to complete, then check your Object Schema. This provides you with an opportunity to confirm that:

    • The source credentials are accurate, and the necessary permissions have been granted.

    • The Jira credentials are verified and correct.

    • The Object Schema has been configured without any issues.

    After clicking the test import button, wait for the process to finish for a few minutes, and then check your Object Schema.

    To monitor the progress, click the “Status” button to view the import execution status.

    3. Full Import

    If you are satisfied with the outcomes of the test import, please proceed to execute a Full Import.

    Pro Tip:

    • Please be aware that importing a large number of records may require considerable time. We recommend conducting this process during off-peak hours when JSM Assets is less frequently utilized.

    • Refrain from clicking the Test Import and Full Import buttons in quick succession; ensure that the first import has completed before initiating the next. JSM Assets does not accommodate multiple simultaneous imports.

    Important Note: Daily Imports

    Daily imports are typically scheduled during late-night hours (00:00-06:00), when the system is under lighter load. However, keep in mind that these hours are also used by Atlassian for JSM/Assets version updates. If there's a conflict, the import process may fail, and you will see an error message in your logs.

    To ensure smooth operation, check your import flow daily and enable the Notify Me feature to receive alerts if an error occurs (https://piosoftware.atlassian.net/wiki/spaces/WS/pages/28508261 ). We highly recommend reviewing the Operational Tips provided on the following page:https://piosoftware.atlassian.net/wiki/spaces/WS/pages/2654212