ITAS Integration
ITAS Integration helps authorized development teams manage project workflows directly from Visual Studio Code.
Features
- Sign in with an authorized ITAS account.
- View and select assigned Jira user stories.
- Automatically fill branch details from the selected story.
- Create or update development branches.
- Upload complete project folders when required.
- Select one or more individual workspace files using an Explorer-style tree.
- Upload exactly the checked files while preserving their workspace-relative paths.
- View the component list stored in the selected Jira user story.
- Open the related workflow in ITAS after a successful operation.
- Remember the current and most recently used Jira story.
Requirements
- Visual Studio Code 1.95.0 or newer.
- Access to an authorized ITAS environment.
- A trusted workspace containing the project files to process.
Connection and access details are provided by your organization’s ITAS administrator.
Getting started
- Install the extension.
- Sign in with your authorized ITAS account.
- Select an assigned Jira story.
- Open the branch workflow.
- Upload complete folders or select only the required files.
- Review the result and open the related workflow in ITAS when needed.
Available commands
- ITAS: Login
- ITAS: Logout
- ITAS: Create/Update Branch
- ITAS: Open Current Story in Git Management
- ITAS: Select Current Jira User Story
- ITAS: Refresh Assigned Jira User Stories
File selection
The extension supports two upload modes:
- Select Folders and Upload for complete project folders.
- Select Specific Files for choosing files from
force-app and vlocity while retaining their original project structure.
Only the force-app and vlocity trees are displayed. Each file is selected independently. The extension does not automatically add companion files, so selecting one .cls, -meta.xml, or other file uploads only that selected file.
Support
Contact your internal ITAS administrator or development-support team.
License
MIT
Server-side workflow order
After the extension uploads selected folders or files, the API runs the following sequence:
Create/Update Branch -> Conditional Salesforce Checks -> Jira Update
Branch Validation and PMD run only when the uploaded ZIP contains force-app files. Vlocity-only and RLM-only uploads skip both checks and continue to Jira. When Salesforce checks run, Jira is skipped if either one fails.
