Skip to content

Jira and change tickets

BreachSpider does not create Jira issues automatically. It helps you write the change ticket and get it into Jira (or any ticketing system) yourself:

  • Draft a change ticket from a Fix first action, or from one device's fix plan in Assets. The assistant (Claude, by Anthropic) drafts it from the vendor statements BreachSpider holds, every step cites its source, and the scope (devices, sites, owners, maintenance windows) comes from your inventory. See Fix first.
  • Send it: copy it, email it to members of your organization from BreachSpider, or open it in your own email program (for example to a Jira or service desk inbox that turns emails into issues).
  • Export every action as CSV from Fix first (Export change tickets) and import the file with Jira's CSV importer. Each row has the action, target version, devices, sites, owners, maintenance windows, what it clears and the fix source.

Recording the work itself is in Maintenance: a work order can be linked to the Fix first action it carries out, and completing a firmware update re-checks the device.