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 selected story directly in the ITAS DevOps Assistant 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

1. Install the extension.
2. Sign in with your authorized ITAS account.
3. Select an assigned Jira story.
4. Open the branch workflow.
5. Upload complete folders or select only the required files.
6. Review the result and continue the selected story in the ITAS DevOps Assistant.

Available commands

• ITAS: Login
• ITAS: Logout
• ITAS: Create/Update Branch
• ITAS: Open Current Story in DevOps Assistant
• ITAS: Select Current Jira User Story
• ITAS: Refresh Assigned Jira User Stories

File selection

The extension supports two upload modes:

• Select Folders for adding complete project folders to the staged selection.
• Select Specific Files for choosing files from force-app and vlocity, plus the optional root-level package.xml and packExport.yaml manifests.

Each file is selected independently and retains its workspace-relative path. If Salesforce or Vlocity components are selected without their corresponding manifest, the extension asks for confirmation before starting the branch workflow. Manifest files, when included, must be named exactly package.xml and packExport.yaml and must remain at the workspace root.

DevOps Assistant handoff

After a successful branch workflow, the extension can open the selected Jira story in the ITAS DevOps Assistant. The handoff includes the authenticated user ID, Jira key, created branch, repository, target branch, source alias, and the component auto-fetch preference. Credentials are exchanged only through the one-time browser-login ticket and are not placed in the Assistant URL.

The Assistant context can be configured with:

• itasintegration.assistantRepository
• itasintegration.assistantTargetBranch
• itasintegration.assistantSourceAlias
• itasintegration.autoFetchAssistantComponents

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 -> Branch Validation -> PMD -> Jira Update

The Jira update is skipped when Branch Validation or PMD fails. The authenticated ITAS user ID is used for both validation jobs.