Push Incidents from Jira to Drata

This Tines story eliminates manual compliance evidence collection by automatically pulling a Jira ticket and uploading it as mapped evidence to the correct control in Drata, triggered by a simple form submission.

---

What You'll See:

• A web form collects a Jira ticket number, Drata workspace ID, and control ID from the user
• Tines fetches the full Jira issue details via the Jira REST API
• The Jira response is transformed into a structured JSON format
• The formatted ticket is uploaded as external evidence to the specified control in Drata, with creation and renewal dates automatically set

---

Perfect For:

• GRC and compliance teams: Mapping resolved incidents to specific compliance controls during audit cycles without manual file exports
• Security operations teams: Quickly attaching Jira-tracked remediation work as evidence to Drata controls after closing out vulnerabilities or incidents
• Compliance engineers managing SOC 2 or similar frameworks: Reducing repetitive manual evidence uploads across multiple Drata workspaces and controls

---

Requirements:

• Jira — with API access enabled and an active API key
• Drata — with an active API key scoped for read and write access across Controls, Users, and Personnel
• The following configured in Tines:
  • ◦ jira credential — your Jira API key
  • ◦ drata credential — your Drata API key
  • ◦ jira_domain resource — your Jira instance domain
  • ◦ jira_username resource — your Jira username