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.7

JIRA
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: JIRA is an issue and project tracking software platform. This technology is designed to assist development teams in planning, assigning, tracking, reporting, and managing work. JIRA supports multiple workflow types such as agile software development and customer support. This technology automatically updates issues and transitions work when code is committed. Additionally, this product supports contentious integration and deployment functionalities.

JIRA requires a relational database in order to store issue data. If the user is setting up a completely new JIRA installation, users have the choice of configuring a connection to an internal, embedded, H2 database, or an external connection to a Microsoft Structured Query Language (SQL) Server, MySQL, PostgreSQL, or Oracle database. The vendor states that the H2 database should only be used for evaluation purposes and strongly recommends connecting JIRA to one of the aforementioned TRM-approved external databases.

This technology is available as a cloud-hosted solution, an on-premise solution, and as a mobile application. This entry covers the on-premise solution only.

This technology is available in four editions, Free, Standard, Premium, and Enterprise. This entry covers all four editions.

This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: https://dvagov.sharepoint.com/sites/OITMT/SitePages/MTHome.aspx

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: https://dvagov.sharepoint.com/sites/OITECSO
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 been assessed by the Section 508 Office and found non-conformant. 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 Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision: View Decisions
Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v24.6
Decision Date: 06/03/2024 at 16:54:56 UTC
Introduced By: TRM Request
Vendor Name: Atlassian Software Systems
- The information contained on this page is accurate as of the Decision Date (06/03/2024 at 16:54:56 UTC).