Versions Compared

Version Old Version 12 New Version Current
Changes made by

Pio

Eva Ruzheva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

1

...

. Build Objects/Attributes

Once you completed After completing the Source and Destination configurations, it is 's time to create Object Types and their relations according to relationships based on the Azure AD data model.

You may can also choose to enable or disable Object Schema sharing.

Info

Pro Tip: Commonly, Many of our customers create references from other Object Schemas and are in need of accessing access to the Azure AD data. We recommend enabling the Object Schema sharing.

Review the options and , then click the "Build Objects/Attributes" button.

Screenshot 2024-07-10 at 09.29.15.pngImage Removedimage-20250210-112955.pngImage Added

Note

This step only 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 stepcompleted 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.

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

...

The Object Schema Graph will be as follows:

Screenshot 2024-07-10 at 09.34.07.png

2

...

. Import

You can test the configuration by clicking the Test Import button. This test will import the first 100 Entra ID (Azure AD) Users to users into your Object Schema. After the test run runs, wait for a few minutes for the process to finish and complete, then check your Object Schema.

You may To monitor the progress, click the Check Import Status button to check view the import execution status.

Screenshot 2024-07-10 at 09.37.32.pngImage Removed

image-20250210-113414.pngImage Added

If you are happy with the results of the test run, please run a manual full import.

Please note that there is one known and accepted limitation.the following known limitation:

Note

Known Limitation

A user can have max be mapped to a maximum of 20 groups mapped.

If your users are members of more than 20 groups then , you may can follow the step-by-step guide forhere:

Mapping Azure AD (Entra ID) Users with Jira Users and Jira Groups

Contact Alternatively, contact us to find discuss the best option solution for your site.

Info

Pro Tips:

  • You can select the data types (Object Types) and user properties (Attributes) you wish to import, helping reduce the amount of data transferred to your Assets. For more details, refer to our guide: Admin Configuration .

...

  • Please note:
    If you have a large number of Azure AD users or groups, the import may take some time. We recommend testing the import during off-peak hours when JSM Assets is not heavily used.

  • If you haven’t filtered Users and Groups on the Source tab, now would be a good time to configure those settings before clicking the Start Import button.

3. Schedule

You have 3 4 options for the scheduling.

Screenshot 2024-07-10 at 09.46.53.pngImage Removedimage-20250210-114122.pngImage Added
Info

Pro Tip:

  • We recommend importing manually first starting with a manual import by clicking the “Full Import“ Import” button and measuring to measure the import duration. In case a

    If the full import takes long an extended amount of time (ie.eg. more than , over an hour), or if there are multiple imports are scheduled at the same time simultaneously in your JSM Site, then hourly scheduling may not be the best option. Prefer Daily scheduling in such case ideal. In such cases, we suggest using Daily scheduling, which is the most common commonly used import schedule among the JSM customers.

Note

Important

note regarding daily imports

Note: Multiple Daily Imports

When scheduling multiple imports per day, ensure there is a gap of at least 3 to 4 hours between each one. It's also best to schedule imports during periods of low JSM Assets usage to minimize impact on performance.

Note

Important Note: Daily Imports

Daily imports are commonly typically scheduled for during late-night hours (00:00-06:00), when there is no heavy load on the systemthe system is under lighter load. However, it is also good to know keep in mind that these times hours are also used by Atlassian for the JSM/Assets version updates by Atlassian. In case If there is 's a conflict, the import process fails. You would see the may fail, and you will see an error message in your logs. Please

To ensure smooth operation, check your import flow daily and configure enable the Notify Me feature if you want to get notified when there is to receive alerts if an error occurs. We highly recommend following reviewing the Operational tips Tips provided on the following page: Operations