How to reference user profile fields?

[Ryan Bullock]

I am working on our change management workflow in Jira Service Managment and would like to have an approver step where the approver is automatically set based on the assignee's manager. Currently we have this information sync'd from Azure AD so it appears in their user profile. Is there a way to reference these fields for automations and filters?

[Eduardo Oliveira - Mindpro Apps]

Hello @Ryan Bullock - nice to meet you 👋🏻

If you’re open to use a third-party app I would like to recommend a powerful and cost-effective solution - Mindpro Sync - User Attributes from OKTA, Azure & OneLogin

This app allows you to integrate with identity providers like Okta, Azure AD, and OneLogin to display user attributes inside Jira and JSM issues (and Portal) and automatically assign approvers based on user hierarchy or via workflow post function.

Additionally you can:

• You can choose to display data for the issue Reporter, Assignee or any other User field
• Select and map the user attributes to be displayed in Jira issues or JSM requests
• Show user hierarchy in issue panel and JSM requests to facilitate escalation and approvals
• Use these attributes data to create JQL queries, filters, dashboards, create JSM queues,
• use in advanced automations, and more.
• And more!

This app has a 30-day free trial version with full support and onboarding assistance included. If you want, we'd love to offer you a live demo where you can talk about your specific needs.

Hope it helps,
Eduardo, from Mindpro team

[Katarzyna Szumilas_Deviniti_]

Hi @Ryan Bullock

If you store your user data in Azure Active Directory you might be interested in a solution developed by my team -> Azure AD Attributes for Jira.
The app matches your Jira users with their accounts in Azure AD and lets you display their properties in dedicated panels on issue and request views, as well as copy them to custom fields of different types (which you can further use in automation).
The mentioned use case of using Manager in the approval process is in fact very common among our clients! The configuration takes only minutes and has been described here.

Feel free to try the app or book a demo session. Our team will be happy to assist :)

Best regards,
Kasia from Deviniti

[Dam]

Hi @Ryan Bullock 

For Automation you can try to find the correct property to be able to get the manager using smart values, the doc is here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/#Entity-Properties

Maybe something like...:

{{assignee.properties.manager}}

I never try that and I can't test it now, but you can dig around that I think... 

You can also check a user profile in your cloud platform to see if there is properties on users or not... 

Entity properties can only be set via API calls using the /rest/api/3/user/properties REST API. Note that this is not the same as the legacy User Properties feature found in Settings > User management > Show details > Edit Jira properties.

I hope this can help a bit... 

Dam. 

[Ryan Bullock]

Unfortunately, the user properties do not match up to those fields I mentioned in their profiles. The user's Jira properties are blank, so the smart values that use {{assignee.properties.XX}} do not return anything.

I have not found a way to reference these in the documentation or sync the user properties with those coming in from Azure AD.