oolak / Use cases / Assignment
Assignment

Who is supposed to fix this?

A finding without an owner never gets fixed. oolak uses simple rules to send each finding to the team responsible for that system, and opens the ticket where that team already works.

All your tools, connected in one place.
Today

What usually happens

  • Security sends long spreadsheets to IT, and IT sends them back.
  • Tickets are opened by hand and go to the wrong queue.
  • When a server changes hands, its findings are left behind.
With oolak

What changes

  • Every finding has a team and a deadline.
  • IT works in its own tool and never sees a spreadsheet.
  • Ownership follows the asset when it changes hands.
With oolak

How it works, step by step

  1. Write a rule once

    Define who owns what by site, group, application or asset type.

  2. Preview before applying

    See exactly which findings a rule will assign before you turn it on.

  3. Open the ticket

    Tickets are created in Jira, ServiceNow, OpenText SM, Monday or Trello, with everything the team needs.

  4. Keep tickets in sync

    When a finding is fixed, accepted or reopened, its ticket follows automatically.

See oolak on your own data in 14 days.

We install oolak in your environment, connect your tools and show you your real risk picture. You keep everything it finds.

Start a free 14-day trial → Try the live demo
For engineers

Technical details

How do assignment rules work?
Rules match on asset and finding attributes and assign a work team. Each rule has a dry-run preview, and through the API or the AI assistant a rule can only be applied after its preview is confirmed.
Which ticketing systems are supported?
Jira, ServiceNow, OpenText Service Manager (HPSM), Monday, Trello, GitHub and GitLab issues, and any system that accepts a webhook.