Click Test to ensure the details are correct for Uleska and Jira to be linked
Your Jira authentication will be shown in the Authentications screen
After connecting Uleska to Jira, there will be an additional Jira tab when editing a Version of an Application.
Select your Jira Authentication, which should be what you had entered when setting up - your Jira Username
Specify Project ID, which allows different Versions to be specified to different projects within Jira. This will depend on your Jira configuration, but you can use the APIs and the information within Jira to work out your Project ID to enter here
For new issues, the Issue Type ID will also be found in Jira, to specify that this is the type of issue that is created whenever a new Vulnerability is found. The Uleska platform contacts the Jira platform when a new Vulnerability has been found by the testing tools that was not in the previous scan
Transition ID is used when you are modifying an issue from new to fixed, as Uleska runs various tests and finds that a Vulnerability no longer exists, that existed in the previous scan. It will consider it fixed and will use the *Transition ID* to transition from the state of the previous Vulnerability into this new, fixed state
Click Save. Now every time a new Vulnerability comes up, it will be flagged in your Jira system as well