Cost work in the ticket system
Connect Jira, open tickets from recommendations manually or by policy, and keep recommendation status and ticket status in agreement without a polling cron.
4 lessons. 1 quiz.
Read in order, or jump to what you need.
Connecting Jira
By the end of this lesson, you will be able to connect Jira, explain why classic and scoped API tokens behave differently, and predict which capabilities a scoped token leaves unavailable.
A ticket from a recommendation
By the end of this lesson, you will be able to open a Jira ticket from a recommendation, explain what the fingerprint dedup guarantees, and predict how assignee resolution behaves.
Policy-gated auto-ticketing
By the end of this lesson, you will be able to configure the open_ticket policy effect, size its volume before saving, and work within the one-effect-per-scope constraint.
Bi-directional sync
By the end of this lesson, you will be able to trace status and ownership changes in both directions, explain how the loop guard prevents ping-pong, and name the deferred limits.
Module quiz.
Take it once the lessons are done.