Hello Veracode users! Here are the highlights from the release notes over the past week: 

Dynamic Analysis 

Prescan workflow improvements, including: 

• The prescan option has moved to the Schedule page. In addition, you can now use the new prescan-only option if you want to verify your configuration before submitting the analysis. 
• A new option on the Schedule page to enable you to save your Dynamic Analysis configuration and continue working on it or submitting it later. 
• Icons have replaced the menu in the individual rows of the URLs table, providing greater ease of use when you want to edit the configuration, link to an application, or delete the URL. 

Platform 

• New Team Admin Role  
  • A new Team Admin user role that an administrator can grant to users.  
  • With the Team Admin role, you can create, edit, and delete users within the teams you manage.  
  • This new role makes it easier for organizations to manage permissions for many users. 
  • 👉 Learn more from @Tim J (Veracode PM) (Veracode)​'s product update 
• New Mitigation Type  
  • A new mitigation type that allows you to propose mitigations using the mitigation type Mitigated - Referred to Library Maintainer.  
  • You can classify findings related to libraries developed by another development team (who may build libraries in-house, but may not own the application Veracode is scanning) 
  • 👉 Learn more from @Tim J (Veracode PM) (Veracode)​'s product update 

Jira Integrations 

Findings import options now available Veracode Integration for Jira version 3.23.0: 

• Automatically assign imported findings to a Jira epic or link them to a related issue. 
• Map string, number, and date/time data types from Veracode fields to text, number, and date/time field types in Jira. The integration imports the values from the Veracode fields to fields in Jira issues.