Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.2

ScriptRunner for Jira
ScriptRunner for Jira Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: ScriptRunner for Jira provides the capability to automate bulk actions, create scripted fields, build workflows, and integrate third-party applications in Jira. This technology allows users to archive issues, update and validate custom fields across projects, and run scripts on a schedule, on-demand, or in response to an event within Jira. ScriptRunner for Jira provides functionality for further control of Jira instances through allowing direct access to the Jira Java Application Programming Interface (API) (for Server and Data Center) and REST API (for Cloud).

This technology can optionally utilize multiple databases, including Oracle Database, Microsoft Structured Query Language (SQL) Server, PostgreSQL, and MySQL databases.

This technology is available in three editions, ScriptRunner for Jira Server, ScriptRunner for Jira Datacenter, and ScriptRunner for Jira Cloud. This entry only covers ScriptRunner for Jira Server and ScriptRunner for Jira Datacenter as the Cloud edition is updated separately and offers different functionality.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v22.9
Decision Date: 09/02/2022 at 19:57:52 UTC
Introduced By: TRM Request
Vendor Name: Adaptavist
- The information contained on this page is accurate as of the Decision Date (09/02/2022 at 19:57:52 UTC).