System
Jira, Microsoft Entra ID
App: User Profiles for Jira (Microsoft Attributes Sync)
Short description
Optimize work and approval processes by syncing Microsoft Entra ID attributes into Jira and using the manager attribute to route requests automatically and keep workflows efficient.
Challenge
Approvals in Jira - such as purchase orders, can be delayed when the right approver isn’t clear or notified, causing back-and-forth and inefficiencies. With Microsoft Entra ID attributes synced into Jira, it is possible to optimize the approval process by using the manager attribute, routing requests to the correct approver and speeding up decisions.
Actors
👔 John – Employee
👤 Alex – HR Manager
🛠️ Taylor – IT Admin
Actors Goals
John (Employee) – Wants his purchase request approved by the manager without chasing for updates.
Alex (Manager) – Wants to be notified directly in Jira when an approval is required, without extra confusion.
Taylor (IT Admin) – Wants reliable synchronization of manager attributes from Entra ID so workflows always run smoothly.
Use Case Scenario (step-by-step)
-
John creates a purchase request in Jira for a new laptop.
-
The workflow contains an approval step, with the approver set to the manager attribute from Microsoft Entra ID.
-
Alex, John’s manager, is automatically assigned and notified in Jira to approve the request.
-
Alex reviews and approves the purchase directly in Jira.
-
Taylor, the IT Admin, ensures that manager attributes remain synchronized from Entra ID so the workflow continues to route requests reliably.
Outcome
-
Employees like John get their requests routed to the right approver without delays.
-
Managers like Alex receive clear approval tasks, avoiding missed updates.
-
IT Admins like Taylor keep processes reliable with synchronization in place.