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 the connection HackenProof -> GitLab issue works
  • How to create a GitLab issue
  • How to connect the GitLab repository to the HackenProof program
  1. Welcome
  2. Integrations

GitLab Issue

Automatically create GitLab issue from HackenProof for reports with any status

PreviousGitHub IssueNextVDP iFrame

Last updated 1 year ago

How the connection HackenProof -> GitLab issue works

This guide explains how GitLab connection helps companies when they run a bounty program at HackenProof.

Once you connect your bug bounty program to your GitLab repository (public or private), you can automatically create a GitLab issue:

remember, you can create a GitLab issue for reports with any STATUS

How to create a GitLab issue

  • Open the report you want to create a GitLab issue from

  • Navigate to the prerequisites section of the report and find the GitLab issue section

  • Press the Create GitLab issue button. As a result, the appropriate issue will be created in your GitLab repository.

  • Also, in the report's GitLab section, you will find the link to the newly created issue:

How to connect the GitLab repository to the HackenProof program

  • Open your HackenProof program, which you want to connect to HackenProof

  • Navigate to the Integrations tab and open GitLab app

  • Connect your HackenProof program to GitLab by specifying the Repository URL and your GitLab API token.

Repository URL. Be sure you use the correct Project ID (not name). Here is a correct sample: https://gitlab.com/api/v4/projects/19980000/issues, where:

  • https://gitlab.com/api/v4/projects/ - core of our integration

  • 19980000 - project ID (not a name)

  • issues - repo issue page

GitLab API token. To create your token: GitLab Project Settings -> Access Tokens

  • Generate personal access token.

Make sure to copy your personal access token now. You won’t be able to see it again!

Once you specified Project URL and your GitLab token you can connect your bug bounty program with GitLab and start creating GitLab issues