HackenProof Docs
  • Welcome
    • HackenProof
      • Services we provide
      • Our resources
    • Integrations
      • Slack
      • Discord
      • Telegram
      • Zapier (Webhook)
        • Zapier -> Lark
        • Zapier -> Linear
        • Zapier -> Jira Service Management
        • Zapier -> PagerDuty
        • Zapier -> Google Chat
        • Zapier -> ClickUp
      • Jira Software
      • GitHub Issue
      • GitLab Issue
      • VDP iFrame
    • FAQ
      • Audit & Bug Bounty (BB)
      • Crowdsourced Audit & BB
      • Penetration testing & BB
    • Emergency
      • Reset 2FA
    • Code of Conduct
    • Referral Program
  • Bug Bounty
    • Bug Bounty process
    • How to start Bug Bounty
    • How to create a VDP
    • Vulnerability classification
      • Web & Mobile
        • Out-of-Scope Bugs
      • Smart contracts
      • Blockchain protocols
    • Reports Basics
      • Points Guide
      • Crafting a well-readable report
  • Dashboard
    • Company dashboard
      • Manage programs
      • Manage reports
      • Share report
      • Labels
      • E2E report encryption
      • Reports decrypting with Mailvelope
      • Users and roles
      • Program/Report Assignee
      • Replenish your balance
      • Integrations
    • Hacker dashboard
      • 👉How to start
      • Submit a report
      • Reports Basics
      • Vulnerability classification
      • 👮‍♂️KYC
      • Сreate a crypto wallet
      • 💸Withdraw bounty
      • Hacker Leaderboard
      • Reset 2FA
      • 🍕HackenProof community
      • Report ID
      • Private Program
      • Contact support
    • Company-Auditor dashboard
      • How to start
      • Add members
      • Submit report
      • Contact support
  • Crowdsourced audit
    • Audit process
    • How to start Audit
    • Supported tech
    • Vulnerability classification
    • Reports Basics
    • Qualified Auditors
    • Judging / Triaging
      • Targets
      • Team
    • [CA] Bounty Distribution Rules
    • Fee & Payments
  • DualDefense Audit
    • What is DualDefence Audit
    • General Guidelines
    • How DualDefence Audit goes
    • Contest Phases
    • Vulnerability classification
      • [DD] Smart Contracts
    • [DD] Bounty Distribution Rules
  • good to know
    • Changelog
    • Branding
    • Vulnerability Disclosure
  • Education
    • Courses
    • Tools
    • Useful sources
Powered by GitBook
On this page
  • How works the connection HackenProof -> Jira
  • How to manage reports in Jira
  • After you fix the reports
  1. Welcome
  2. Integrations

Jira Software

Automatically create tickets in your Jira Software for reports from HackenProof with the status Triaged

PreviousZapier -> ClickUpNextGitHub Issue

Last updated 1 year ago

How works the connection HackenProof -> Jira

HackenProof uses a ticket-based system that has processing. And when the report is considered valid, it proceeds to the TRIAGED stage.

We believe the company may need to connect its HackenProof bounty program to its Jira to work on valid reports to fix them.

  • Once you connect your bounty program to Jira, it will create a Jira project with the same name as your HackenProof bug bounty program.

  • Then, all reports that are marked as TRIAGED will appear in your Jira project.

Note #1. Only reports with state TRIAGE will appear in the Jira

How to manage reports in Jira

The report/ticket management process and the type of boards you intend to use in Jira depend on your team.

For example, it can be a Kanban board with the following flow:

After you fix the reports

Please remember, after developers fix the report, it must be manually marked as RESOLVED in your HackenProof program.

different stages of reports