A practice is a mechanism for monitoring and enforcing development and testing policies. This practice defines expectations around the acceptable number of defects (or "bugs") in a JIRA project. This ensures that a large numbers of bugs are not left unattended. 

In this section:


  • DTP 5.3.3 or later

  • DTP Enterprise Pack 5.3.3 or later


See Downloading and Installing Artifacts.

Flow Configuration

  1. Import the practice into a service and configure all JIRA http request nodes to connect to your system. The nodes will be flagged with a red triangle.

  2. Double-click a node and click the edit icon in the Configuration field.

  3. Specify your connection to JIRA when prompted.  

    Create a Dedicated JIRA User for Extension Designer

    If JIRA detects that a user is making requests from multiple machines, it may lock the user out. We recommend creating a dedicated user for Extension Designer to avoid being locked out by JIRA.   

  4. After configuring the first node, you can choose the connection settings in the other nodes from the Configuration drop-down menu so that you don't have to reenter the settings for each node.

  5. Deploy the practice and configure the JIRA WebHook.

Adding Custom Issue Types

You can configure the flow to include any custom issue types used in your organization. By default, the practice tracks JIRA Bugs. 

  1. Double-click the Configure Defect Issue Types change node and click the edit button in the Rules section. 

  2. Define your custom types in JSON editor and click Done

JIRA WebHook Configuration

Configuring the JIRA WebHook to connect to a deployment of the Defects for JIRA Practice requires JIRA Administrator Privileges.

  1. After deploying the practice to Extension Designer, click on the service category in which the artifact was imported and deployed (e.g., Practices).
  2. In the Available Endpoints section, expand the JIRA WebHook endpoint and copy the address.

    Getting the WebHook Endpoint when Authentication is Enabled

    When authentication is enabled in the Server Settings, you will need to use the direct service port and node ID in your JIRA WebHook request.

    1. Get the port number from the service category page:
    2. Replace the port number in the endpoint URL with the practices port number and truncate the path to reference the endpoint directly:

      Original endpoint URL with service ID:

      Direct endpoint URL to use in step 5:
  3. In JIRA, click on the settings gear icon and choose System from the JIRA ADMINISTRATION menu.

  4. Click WebHooks in the Advanced section of the System administration page.

  5. Create a new WebHook and paste the path to the Defects for JIRA WebHook endpoint into the URL field.


    After deploying the Defects for JIRA practice, moving the nodes for the practice to another flow or service in Extension Designer will change the path to the WebHook endpoint. Be sure to change the URL in the JIRA WebHook menu if you decide to move the practice to another flow or service.
  6. You can now configure the types of events that you want your WebHook to broadcast to the Defects for JIRA Practice. Leave the JQL field empty so that transition between issue types can be detected.


The WebHook has now been configured and should broadcast to the WebHook endpoint when Bug Issues are created, updated, or deleted.

Adding the Practice to Your Policy

After installing the practice and configuring the JIRA WebHook, you can add the practice in Policy Center to start automatically monitoring activities. See Adding a Policy for instructions on how to add practices to policies.

The artifact dynamically queries JIRA and returns a list of projects, defects states, and severities used in your system so that you can configure the rules for the practice:

  1. Choose a project from the JIRA Project drop-down menu. 
  2. Enter an upper limit for defects and choose a state from the Defects in drop-down menu.
  3. Choose which severities the practice should apply to.

You can add additional instances of the practice to create more sophisticated policies that accomplish your development goals.

  • No labels