Configure rules in the agile tool configuration

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read

    • Jira issues are created on the Jira platform if the records created in the Application Vulnerable Item, Container Vulnerable Item, Application Remediation Task and Container Remediation Task match the rules created in the agile tool configuration.

    Before you begin

    Roles required: sn_vul.app_read_all, sn_vul_container.read_all, sn_vul_agile.agile_tool_admin or sn_vul_jira.admin.

    Procedure

    1. Navigate to All > Agile Management for VR > Configure Agile Tools.
    2. To create configuration rule in the Agile Tool Configuration, select New.
    3. On the form, fill in the fields.
      Table 1. Agile Tool configuration form
      Field Description
      Name Name of the Agile Tool Configuration.
      Order Order of the Agile Tool Configuration.
      Agile Tool The agile tool to create issues on the specific agile platform.
      Entity Table Table on which the Configuration rule is to be applied.
      Condition Filter condition on the selected entity table to create Issues on the Agile platform.
      Auto Issue Creation The configuration rule will be queried when any new record is created in the selected entity table, only if the check box is selected.
      Note:
      The user must use list action to create issues for existing entity records.
      Project The project in which the Jira Issue will be created.
      Issue Type The type of issue to be created in a particular project.
      Assign To The assignee to whom the issue should be assigned on creation of the issue. To keep the created issues as unassigned, select “None”.
      State Mapping The existing state mappings from the Agile Tool State Mapping table or create state mapping between the issue status in the agile platform and the ServiceNow entity table states.
      By default, when the application is installed Application Remediation Task and Container Remediation Task are displayed in the Entity Table field on the Agile Tool Configuration form.
    4. To add the Application Vulnerable Item and Container Vulnerable Item in the Entity Table list navigate to System Properties > sn_vul_agile.tablesToShow and add all in the Value field.
      Table 2. System property form
      Field Description
      Choices Comma-separated values for a list.
      Value Set the desired value for property. All property values are stored as strings. When retrieving properties via the gs.getProperty() method, treat the results as strings.

      For example, a true|false property returns 'true' or 'false' (strings), not the Boolean equivalent.
    5. Select the existing state mapping record or create state mapping in the Agile Tool State Mapping.
      Table 3. Agile Tool State Mapping form
      Field Description
      Name Insert the unique name of the State Mapping.
      Agile Tool Select the agile tool.
      Entity Table Select the source table on which state mapping will be created.
      Project Select the project in which the state will be mapped.
      ServiceNow Entity State Select the state that you want to map with agile tool status.
      Agile Tool Status Select the state that you want to map from vulnerability item states.
    6. Select Save and Fetch Projects to fetch the projects in the Project field Configuration rule and validate the credentials of the Agile tool.
      Tip:
      You can set the System Property projectsPageSize to fetch a particular number of projects per page.
    7. Navigate to System Properties > sn_vul_jira.projectsPageSize and add the number of projects to be fetched per page in the Value field for Jira Cloud.
    8. Select the Project, Issue Type and Assign to in the Configuration rule after the projects are fetched.

      Default field mapping will get populated in the embedded list of Agile Tool Field Mappings. By default, Summary and Description fields of Issues are mapped.

    9. To map other issue fields with the ServiceNow fields, select Add Field Mapping.
      Note:
      • You must map String and Choice type fields only.
      • Make sure all the mandatory issue fields from the Agile tool are mapped properly with the entity field.
      Table 4. Agile Tool State Mapping form
      Field Description
      Issue Field Contains the issue fields of the currently selected project and issue type in the Configuration Rule.
      Entity Fields Contains the fields of the entity table selected in the Configuration Rule.
      Use the Script Select to use the script for mapping the issue fields with entity fields.
      Script Script to map the Issue Field with Entity Fields.
    10. Select Submit in the glide modal to submit the field mapping record in the Agile Tool Field Mappings table.
      Note:
      If you do not map the mandatory fields, issues will not be created for that configuration rule.
      Mandatory fields are displayed on the top in the Agile Tool Configuration form.
      All the field mapping for a particular Configuration rule are displayed in the embedded list of the Agile Tool Field Mapping table in the Agile Tool Configuration table.
    11. Right-click in the header to save your changes.
      The saved record is visible in the Agile Tool Configuration table. If any record is created in the Application Vulnerable Item, Container Vulnerable Item, Application Remediation Task and Container Remediation Task matches any Configuration rule the issue will be created for the record according to the mapping in the Configuration rule.
    12. Navigate to System Properties > sn_vul_jira.cloudBulkSize and set the number of issues to be created per batch in the Value field.
      Note:
      Maximum number of issues that can be created per batch in Jira cloud is 50.
      You can set the batch size for creating issues on Jira Server.
    13. Navigate to System Properties > sn_vul_jira.onPremBulkIssue and set the number of issues to be created per batch in the Value field.
      You can also set the error count in the Value field in the system property to process the records in the manifest table to create Jira issues up to a specific error count.
    14. Navigate to System Properties > sn_vul_agile.ManifestErrorCount and set the maximum number of times until which the manifest with error should be processed.