Build-test automation
IntroductionScenario 1 - Creating a simple procedureScenario 2 - Creating a procedure that uses an SCMScenario 3 - Notification, scheduling, and reportingScenario 4 - Multi-agent build and test
IntroductionCustomizing the automation platform UIConfiguring CloudBees CD/ROUsing CloudBees CD/RO in your environmentCloudBees CD/RO Installed tools
IntroductionArtifact managementAuthenticating users for ldap and active directoryAuto-discoveryDefect trackingJob step execution environmentPostprocessorsReportsWorkflow overviewWorkspaces overview
IntroductionIntrinsic propertiesReserved wordsProperty shortcutsProperty error codes
IntroductionAdding a link to a jobCalling a subprocedureChecking the outcome of preceding stepsConditional executionCustom parameter layoutsEmail notificationsExecuting tasks on all resources in a poolFactory proceduresPostp extensionPublishing and retrieving an artifactReserving a resource for the job step durationRunning steps in parallelStep timeouts and steps that always runStoring and retrieving properties in a jobWorking with properties stored in a procedure
Using special characters in object names
Introduction
IntroductionDefining entriesCreate new or edit existing privileges
IntroductionArtifact detailsCreate new or edit existing artifactsArtifact versionsArtifact version detailsEdit an existing artifact versionRepositoriesCreate new or edit existing repositories
Database configuration
IntroductionCreate new or edit existing configurationsDefect tracking reports
IntroductionCreate new or edit existing email configurationsEmail notifiers
Event log
IntroductionJob configurationShortcutsJobs quick view
IntroductionCloudBees CD/RO job detailsJob step details
IntroductionProcedure runsCreate new or edit existing procedureCreate new or edit existing stepsPublish artifact version stepsRetrieve artifact version stepsSend email stepsCreate new or edit existing parameters
IntroductionProject detailsCreate new or edit existing schedulesCreate new or edit existing credentials
IntroductionNested Property Sheet
Reports
IntroductionResource poolsCreate new or edit existing poolsResource pool details
IntroductionSearch resultsEdit existing property settings
Source control
IntroductionUsersCreate new or edit existing local usersUser detailsEdit user settingsGroupsCreate new or edit existing groupsGroup detailsCreate new or edit existing directory providersSingle sign-onTest directory provider
IntroductionCreate new or edit exiting workflow definitionsWorkflow definition detailsRun workflowWorkflow detailsWorkflow logTransition workflow
Introduction Create or modify WorkspacesWorkspace file

Defect Tracking—create new or edit existing configuration

2 minute readAutomation

Use this page to define a new defect tracking configuration or modify an existing defect tracking configuration. A configuration is a collection of properties that define how CloudBees CD/RO communicates with a particular defect tracking system.

After creating a defect tracking configuration, your entry will appear in the table on the Defect Tracking Configurations web page— to see this web page, select the Administration > Defect Tracking tabs.

To create a defect tracking configuration

From the Defect Tracking Type drop-down menu, select your defect tracking system—CloudBees CD/RO integrates with numerous defect tracking systems. Each integration was created using plugin technology.

Click the Submit button and a set of fields is displayed to enter information to create your configuration.

Enter information into the fields as follows:

Field Name Description

Configuration Name

Enter a unique name for this defect tracking configuration—any name you choose.

Description

(Optional) Plain text or HTML description for this object. If using HTML, you must surround your text with <html> …​ </html> tags. Allowable HTML tags are <a>, <b>, <br>, <div>, <dl>, <font>, <i>, <li>, <ol>, <p>, <pre>, <span>, <style>, <table>, <tc>, <td>, <th>, <tr>, and <ul>.

  • For example, the following HTML:

    <p>
<span style="font-family: Arial;">
  <i>Note:</i> For more information about the <b>abc</b> object, see
         <a href="https://www.google.com/">https://www.google.com</a>.
</span>
</p>
    ▼

    renders as follows:

    <i>Note</i>: For more information about the <b>abc</b> object, see https://www.google.com.
    ▼

Login As

  • User Name —This is the name CloudBees CD/RO needs to use to communicate with your defect tracking system. For example, you may be using a special "read-only" user name similar to "Build" for your user name.

  • Password —This is the password for the specified User Name.

  • Retype Password —Type the password again.

  • URL —This is the URL to use to connect to a JIRA server. For example, you might use something similar to: https://10.10.10.10:8080 or https://yourJIRAserver

Click Submit to save your information.

Using the defect tracking integration

  • Go to Projects > select a project > select a procedure.

  • To create a New Step for defect tracking, select the Plugin link.

  • In the Choose Step panel, select Defect Tracking from the left pane, then select the defect tracking system you configured.

    The right-pane now shows the types of steps available for your configuration.

  • Select the step you need and automatically go to the New Step page.

    On the New Step page, notice the Subprocedure section now contains the defect tracking integration you configured and the step you chose.

  • Enter the remaining information to create your defect tracking step.

See the Defect Tracking Help topic for more information.

To edit an existing defect tracking configuration

Modify any of your defect tracking configuration information by "typing-over" any previously entered information. Click Submit to save your modified defect tracking information.

Introduction
Defect tracking reports