
Seamless integration between Bugcrowd and JIRA for optimal vulnerability management
Seamless integration between Bugcrowd and JIRA for optimal vulnerability management
Seamless integration between Bugcrowd and JIRA for optimal vulnerability management
This integration enables you to more easily connect vulnerabilities surfaced through your bug bounty program with your existing JIRA instance, reducing time and manual effort.
Whether working in JIRA or Crowdcontrol all vulnerability details from Crowdcontrol including comments, priority and status changes will be reflected in JIRA, or vice-versa depending on your chosen workflow.
Keep working the way you need, with custom field mapping and integration of multiple JIRA instances.
This integration enables you to more easily connect vulnerabilities surfaced through your bug bounty program with your existing JIRA instance, reducing time and manual effort.
Whether working in JIRA or Crowdcontrol all vulnerability details from Crowdcontrol including comments, priority and status changes will be reflected in JIRA, or vice-versa depending on your chosen workflow.
Keep working the way you need, with custom field mapping and integration of multiple JIRA instances.
More details
Bugcrowd's bi-directional JIRA integration enables the following features:
- Automatic creation of JIRA tickets when a Crowdcontrol submission moves from a ‘triaged’ to ‘unresolved’ state. All accompanying vulnerability detail is also copied to JIRA.
- When a developer moves a JIRA ticket to a ‘closed’ state after resolving a vulnerability, the associated submission will automatically register a closed or ‘resolved’ state in Crowdcontrol
- All activity (comments, priority changes, ect.) on a single submission within Crowdcontrol will automatically be replicated on the associated ticket within JIRA
- All JIRA ticket fields can be mapped to Crowdcontrol submission fields using our advanced custom field mapping settings
More details
Bugcrowd's bi-directional JIRA integration enables the following features:
- Automatic creation of JIRA tickets when a Crowdcontrol submission moves from a ‘triaged’ to ‘unresolved’ state. All accompanying vulnerability detail is also copied to JIRA.
- When a developer moves a JIRA ticket to a ‘closed’ state after resolving a vulnerability, the associated submission will automatically register a closed or ‘resolved’ state in Crowdcontrol
- All activity (comments, priority changes, ect.) on a single submission within Crowdcontrol will automatically be replicated on the associated ticket within JIRA
- All JIRA ticket fields can be mapped to Crowdcontrol submission fields using our advanced custom field mapping settings
Reviews for cloud
(0)Sign in to write a reviewReviews for server
(0)Sign in to write a reviewReviews for Data Center
(0)Sign in to write a reviewCloud Pricing
Server Pricing
Data Center Pricing
Bugcrowd Inc. provides support for this app.
Bugcrowd Inc. provides support for this app.
Vendor support resources
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2019-10-01
Summary
NA
Versions
Version 1 • Jira Server 7.0.0 - 8.5.11 • Released 2019-10-01
Summary
NA
Installation
- Only product or site administrator is able to install this app.
- Log in to your Bugcrowd's user account and connect Crowdcontrol to JIRA.
- Refer to this documentation for more information.
- Only product or site administrator is able to install this app.
- Log in to your Bugcrowd's user account and connect Crowdcontrol to JIRA.
- Refer to this documentation for more information.