Automating Ticket Creation with Atlassian's JIRA

Automating ticket creation with Atlassian's JIRA

Can you automate ticket creation for security vulnerabilities and policy violations that are (unintentionally) shipping out with your code? 

Atlassian’s JIRA platform is close to an industry standard in bug tracking and ticketing. Whether you are agile, use waterfall or develop on an ad-hoc basis, you've almost definitely used JIRA somewhere along the way and would appreciate the intelligence that JIRA packages in this awesome tool.

The Black Duck Hub now integrates with JIRA to add another layer of intelligence to this already smart tracking system with information around security vulnerabilities and custom defined policy violations.

The Black Duck Hub integration with Atlassian’s JIRA brings the best in breed open source security management within the realm of your JIRA instance. Developers can now be automatically informed of security vulnerabilities and/or policy violations sneaking into your production code. The Black Duck Hub discovers security kinks in your open source, and via the JIRA plugin, reengages with engineering to work on remediation. The workflow is simple and follows the following steps: 

STEP 1:

Login into your Black Duck Hub and define policies using the Policy Management module

STEP 1: Login into your Black Duck Hub and define Policies using the Policy Management module

STEP 2:

Login to your JIRA instance, download & install the Black Duck Hub plugin for JIRA

 

STEP 2: Login to your JIRA instance, download & install the Black Duck Hub plugin for JIRA

STEP 3: Configure the Hub with JIRA 

STEP 4:

Map Hub projects to JIRA projects and select the check box for policies for which automatic tickets need to be created

STEP 4: Map Hub Projects to JIRA projects and checkbox policies for which automatic tickets need to be created

STEP 5:

Provide Black Duck Hub component data for issue type ‘Security’ or ‘Policy Violation’

  STEP 5: Provide Black Duck Hub component data for issue type ‘Security’

 

 STEP 5: Provide Black Duck Hub component data for issue type ‘Security’

STEP 6:

Automatic closure of pre-created JIRA tickets on issue resolution or override

STEP 6: Automatic closure of pre-created JIRA tickets on issue resolution or override

The JIRA plugin ensures development teams are pulled in and presented with information at the right time without compromising on the agility and velocity of the release process.

The plugin is available for download on GitHub and works with your existing Hub subscription. If you haven’t already, try the Black Duck Hub for free today and leverage this joint solution today!

Watch a 3 Minute Demo of the Black Duck Hub

 

0 Comments
Sorry we missed you! We close comments for older posts, but we still want to hear from you. Tweet @black_duck_sw to continue the discussion.
0 Comments

MORE BY THIS AUTHOR

Why Binary Risk Management is Similar to Managing Your Wardrobe

| Jan 3, 2017

As we bid adieu to 2016 and welcome 2017, I'm thinking about the shift from the Continuous Integration (CI)/Build step to the binary repository space as a new control point within the software development cycle. Such dramatic changes aren't new in the software world, but what suprises me most

| MORE >

A Sneak Peek into the Black Duck Hub Plugin for Eclipse

| Dec 13, 2016

The Black Duck Hub team is in the process of shipping a Hub plugin to support visibility into the open source contents of your Eclipse workspace. This plugin makes it easier for developers to look at components and sub-components, including declared & transitive dependencies in the context of open

| MORE >