In this chapter, you’ll find a general overview of Azure AD Attributes Sync for Jira features
The app enables you to:
Read the table below to gain an insight into how the features work.
| Azure AD attributes display in the Issue View and Request Details View | Copy data post function | Update attributes post function | Mapping Azure AD data to a custom field | |
|---|---|---|---|---|
| Feature type* | Project feature | Project feature | Project feature | Global feature |
| What does it do? | Displays Azure AD user info in the Issue Details View and Request Details View | Populates Azure AD user info into custom fields | Updates user info in Azure AD based on values from Jira custom fields | Populates Azure AD user info into custom fields |
| How to trigger it? | Configure the Azure AD Attributes panel in the Project Settings | Change the status of a task according to your post function configuration | Change the status of a task according to your post function configuration | Create an issue or make an issue update** |
| When should I use it? | Use it to display Azure AD user details on the issue side panel. You have to configure this feature once for your project and it will automatically display the requested data in every existing issue and newly created issues in the project. |
Use it when you want to copy Azure AD data into Jira custom field only once, upon a workflow transition. Once the data is populated, the app won’t update the custom field again so you can change the data manually. |
Use it when you want to update Azure AD data with values from Jira custom fields upon a chosen workflow transition***. | Use it when you want to have the Azure AD data refreshed with every Jira issue update. |
*Global feature is triggered in any project containing the custom field selected during setup while Project feature is triggered only in the chosen project
**Changing values of the fields and status transitions trigger a mapping
***[Read a use case and learn about the benefits of this feature.
Read more about the features and see the quick guides to get a sense of how they work.
It makes critical employee data readily available on the dedicated app panel, helping teams allocate tasks based on role or department. It also reduces time spent searching for user information.
Go to the Displaying Azure AD data in the Issue View and Request Details View chapter to learn more about this feature.
See the demo below for a quick presentation.
It copies Azure AD data to Jira custom fields upon the configured status transition. It can be used to automatically assign managers as approvers to simplify the approval process by automatically routing tasks to the correct manager, speeding up the process.
Go to the Copying Azure AD data to Jira workflow chapter to learn more about this post function.
See the demo below for a quick presentation.
Below, you’ll find a table representing Azure AD attribute types supported by the Copy data post function and the custom field types to which you can populate them.
| Custom field type | Supported attribute groups |
|---|---|
| Text Field (single-line) | User properties, Custom user attributes, Devices, Licenses, Groups, Roles |
| Text Field (multi-line) | User properties, Custom user attributes, Devices, Licenses, Groups, Roles |
| Text Field (read only) | User properties, Custom user attributes, Devices, Licenses, Groups, Roles |
| User picker (single user) | User properties * |
| User picker (multiple users) | User properties ** |
| Select List (single choice) | User properties, Custom user attributes |
*The User picker (single user) and User picker (multiple users) field types support only the Manager attribute.
Below, you’ll find which attributes from the User properties group can be copied to the Select List (single choice) using the Copy data post function:
It updates user properties in Azure AD with data from Jira custom fields upon the configured status transition.
This post function ensures that the desired modifications are reflected in Azure AD in real-time, maintaining consistency across platforms and reducing the need for manual updates by administrators.
Go to the Updating user’s attributes in Azure AD using Jira workflow chapter to learn more about this post function.
See the demo below for a quick presentation.
Below, you’ll find a table representing Azure AD attribute types supported by the Update attributes post function and the custom field types to which you can populate them.
| Custom field type | Supported attribute groups |
|---|---|
| Text Field (single-line) | User properties, Custom user attributes |
| Text Field (multi-line) | User properties, Custom user attributes |
| Text Field (read only) | User properties, Custom user attributes |
| User picker (single user) | User properties* |
| User picker (multiple users) | User properties* |
*The User picker (single user) and User picker (multiple users) field types support only the Manager attribute.
This feature is triggered every time you make an issue update, so custom fields’ values are regularly updated with the most recent Azure AD user data.
It prevents outdated information from being used in workflows, ensuring that tasks are assigned and tracked based on the most accurate employee details, which is crucial for fast-moving teams.
Changing issue statuses and field values are the only updates that trigger this feature, so there won’t be data changes after adding comments or attachments.
Go to the Mapping Azure AD data to a custom field chapter to learn more about the Mapping feature.
See the demo below for a quick presentation.
Below, you’ll find a table representing Azure AD attribute types supported by the Mapping feature and the custom field types to which you can populate them.
| Custom field type | Suported attribute groups |
|---|---|
| Text Field (single-line) | User properties, Custom user attributes, Devices, Licenses, Groups, Roles |
| Text Field (multi-line) | User properties, Custom user attributes, Devices, Licenses, Groups, Roles |
| Text Field (read only) | User properties, Custom user attributes, Devices, Licenses |
| User picker (single user) | User properties* |
| User picker (multiple users) | User properties** |
| Select List (single choice) | User properties, Custom user attributes |
*The User picker (single user) field type supports only the Manager attribute.
**The User picker (multiple user) field type supports only the Manager and Sponsors attributes.
Below, you’ll find a specific list of User properties attributes supported by the Select List (single choice) field type in the Mapping feature:
To read more about the Azure AD attributes supported by the app, go to the Supported Azure AD attributes chapter.
If you can’t find the answer you need in our documentation, raise a support request.
Back to App page