/
Import Configuration for Tempo Importer

Import Configuration for Tempo Importer

  • In production

    • 1. Build Objects/Attributes

    After configuring the Source and Destination, the next step is to define Object Types and establish their relationships based on the Tempo data model.

    Additionally, you have the option to enable or disable Object Schema sharing as needed.

    Pro Tip: Our customers often create references from other Object Schemas, which require access to Tempo data. For this reason, we recommend enabling Object Schema sharing.

    Review the options and click the Build Objects/Attributes button.

     

    image-20250320-113915.png

    This process is a one-time requirement. Once the build is successfully completed, there’s no need to repeat it. If this step has already been completed, you will receive a notification confirming it.

    You may check your new Object Schema now and make sure the Object Types and Attributes are successfully created.

     

    Screenshot 2024-05-29 at 14.42.30.png

     

     

    The Object Schema Graph will be as follows:

     

    Screenshot 2024-05-29 at 14.44.21.png

     

    2. Test and Full Imports

    You can test the configuration by selecting the Test Import button, which will import up to 100 Worklogs into your Object Schema. This allows you to verify the following:

    • The Tempo access token is valid, and appropriate permissions are granted.

    • The Jira credentials are correct.

    • The Object Schema is correctly configured without issues.

    After clicking the button, wait a few minutes for the process to complete, then review your Object Schema. To monitor the import progress, you can use the Check Import Status button.

    image-20250320-114039.png

     

    If you are happy with the results of the test run, please run a Full Import.

    Pro Tips:

    • If you have a significant number of Tempo users, please be aware that the import process may take some time. We recommend running tests during off-peak hours when JSM Assets is not heavily utilized.

    • Additionally, avoid clicking the Test Import and Full Import buttons consecutively without allowing the first process to complete, as JSM Assets does not support simultaneous imports.

    3. Schedule

    You have four options for the scheduling.

    image-20250320-114131.png

    Pro Tip: We recommend starting with a manual import by clicking the Full Import button to measure the duration of the process. If the full import takes a significant amount of time (e.g., over an hour) or if multiple imports are scheduled concurrently in your JSM Site, hourly scheduling might not be ideal. In such cases, opt for daily scheduling, which is the most commonly used option among JSM customers.

    Important Note Regarding Daily Imports:

    Daily imports are typically scheduled during off-peak hours (00:00–06:00) to avoid system overload. However, these times may coincide with Atlassian's JSM/Assets version updates, which can cause the import to fail. If this happens, an error message will appear in your logs. To stay informed about issues, regularly check your import flow and enable the Notify Me feature under the Admin tab. For more guidance, refer to the Operational Tips Page:

    Operations