Upgrade the App to v1.3.1

For v1.3.1, we have introduced
- 'priorityMapping' parameter to all the ticketing schemes to map the issues created in Jira with appropriate priority based on their risk scores or severity level.
- For the WAS module we are adding 'result' data as an attachment in Jira issues (Please check the Pre-requisites for this change).

To Upgrade to v1.3.1,
1. Stop your containers
2. Update the latest images in docker-compose.yml. You can get the latest YAML file from GitHub.

If you don't want to opt for 'priorityMapping', then you can restart your containers, and Jira Connector will assign default Jira instance priority to all the issues just as earlier.

If you want to opt for 'priorityMapping' then, follow the instructions provided below to update template and then restart the containers.

For 'priorityMapping' to be effective in Jira issues, please update the 'metadata' section of the ticketing template as per your ticketing scheme and profile with priorityMapping JSON. Refer below to learn about priorityMapping for each ticketing scheme. Once a template is updated manually, make sure it's a valid JSON; you can check that using an online JSON validator.

Further, if you don't want to make any manual changes and don't have any customization added to them, then you can delete the template file and restart the connector. It should bring the template with the latest changes.

PriorityMapping per Ticketing Scheme

VMDR - Host_Vuln_Linking_Ticket_Scheme.json (Ticketing scheme)VMDR - Host_Vuln_Linking_Ticket_Scheme.json (Ticketing scheme)

Sample - JSON

"priorityMapping": {
        "parent":{
          "matchWith": "${TRURISK_SCORE}",
          "criteria": {
            "Highest": "850-1000",
            "High":"700-849",
            "Medium": "500-699",
            "Low":"0-499"
          }
        },
        "relatedTicket":{
          "matchWith": "${QDS.content}",
          "criteria": {
            "Highest":"90-100",
            "High": "70-89",
            "Medium": "40-69",
            "Low": "1-39"
          }
        }
      }

VMDR - Per_Detection_Separate_Ticket_Scheme.json (Ticketing scheme 2)VMDR - Per_Detection_Separate_Ticket_Scheme.json (Ticketing scheme 2)

Sample - JSON

  "priorityMapping": {
        "parent":{
          "matchWith": "Jira default",
          "criteria": {}
        },
        "relatedTicket":{
          "matchWith": "${SEVERITY}",
          "criteria": {
            "Highest": 5,
            "High": 4,
            "Medium": 3,
            "Low": 2,
            "Lowest": 1
          }
        }
      }

WAS - Per_Web_App_Finding_Ticket_Scheme.json (Ticketing scheme 4)WAS - Per_Web_App_Finding_Ticket_Scheme.json (Ticketing scheme 4)

Sample - JSON

 "priorityMapping": {
        "matchWith": "${SEVERITY}",
        "criteria": {
          "Highest": 5,
          "High": 4,
          "Medium": 3,
          "Low": 2,
          "Lowest": 1
        }
      }

CS - CS_Container_Link_Ticket_Scheme.json (Ticketing scheme 5), CS_Container_Sub_Ticket_Scheme.json (Ticketing scheme 6), CS_Image_Link_Ticket_Scheme.json (Ticketing scheme 7), CS_Image_Sub_Ticket_Scheme.json (Ticketing scheme 8)CS - CS_Container_Link_Ticket_Scheme.json (Ticketing scheme 5), CS_Container_Sub_Ticket_Scheme.json (Ticketing scheme 6), CS_Image_Link_Ticket_Scheme.json (Ticketing scheme 7), CS_Image_Sub_Ticket_Scheme.json (Ticketing scheme 8)

Sample - JSON

 "priorityMapping": {
                "parent":{
                    "matchWith": "Jira default",
                    "criteria": {}
                },
                "relatedTicket":{
                    "matchWith": "${vuln.severity}",
                    "criteria": {
                        "Highest": 5,
                        "High": 4,
                        "Medium": 3,
                        "Low": 2,
                        "Lowest": 1
                    }
                }
            }

These upgrade instructions are provided in an incremental manner. If you are using a really old version of the Jira connector, to make sure the connector runs smoothly, please check the upgrade instructions for other versions in the guide as well. This will prevent potential upgrade issues due to missing changes in config/templates.