Capabilities and resources configured during loop creation

When you create a loop, the platform automatically provisions resources, installs and configures plugins, generates tokens, establishes integrations, and assigns appropriate permissions to the loop creator and invited members across multiple capabilities.

Capabilities and Configurations

Capability or Plugin Configuration during loop creation
Plan
  • Creates an application in the same teamspace where the loop is created.
  • Sets up email notifications for work item changes.
  • Names the application using the first five characters of the loop name.
Control
  • Creates a repository with the same name as the loop in the organization associated with the teamspace.
Code
  • No resources are created at this stage.
Build

  • Creates a team with the following convention: <TeamspaceName~LoopName>.

  • Creates the following templates:

    • Project

    • Process

    • Source

    • Jobs

  • Creates a job template with basic CI/CD steps.

  • Creates the Deploy and Control integrations.

  • Creates the main project with the naming convention TeamSpace~Loop:LoopName (The UI displays this convention as TeamSpace~Loop) and configures it using the Process and Source templates.

    Note: A project is associated with only one loop.
Test Creates a project with the same name as the loop within the teamspace.
Deploy
  • Creates an application with the same name as the loop and a team named <TeamspaceName~LoopName>.
  • Creates three empty environments: Development, QA, and Production.
  • Creates a template pipeline and an empty application process.
Plan Plugin
  • Installs and configures the Plan plugin in Measure.
  • Installation occurs once; configuration occurs with each loop.
  • Generates a personal access token in Plan which is used to configure the Plan Plugin for Plan-Measure connection.
  • Auto-synchronizes every 5 minutes.
  • Default version: 1.2.3
Control Plugin
  • Installs and configures the Control plugin in Measure.
  • Installation occurs once; configuration occurs with each loop.
  • Generates a personal access token in Control which is used to configure the Control Plugin for Control-Measure connection.
  • Auto-synchronizes every 5 minutes.
  • Default version: 1.1.1
Deploy Plugin
  • Installs and configures the Deploy plugin in Measure during the first loop creation.
  • Generates a personal access token in Deploy which is used to configure the Deploy Plugin for Deploy-Measure connection.
  • Auto-synchronizes every 5 minutes.
  • Default version: 4.1.1
Test Plugin
  • Installs and configures the Test plugin in Measure.
  • Installation occurs once; configuration occurs with each loop.
  • Generates an offline user token in Test which is used to configure the Test Plugin for Test-Measure connection.
  • No auto-synchronization.
  • Default version: 1.0.32
Control–Plan Integration
  • Links repository changes (pull requests, commits, branch creation) in Control to work items in Plan.
  • Pull request titles and branch names should start with the work item ID for proper syncing.
  • Changes appear in the SCM Event section of the work item in Plan.
  • A personal access token in Plan configures a webhook in Control.
Test–Plan Integration
  • Creates work items in Plan from Test Hub via integration.
  • A personal access token in Plan is used for setup.
  • Verify by opening your Test Hub project and navigating to Manage Integration > Change Management.
Test–Control Integration
  • Maps the repository created in Control to the Test Hub project associated with the loop.
  • View it in Test Hub under Manage Configuration > Repositories.
  • Enables Test Hub to pull test assets from Control.
Measure
  • Creates a team <TeamspaceName~LoopName Team> and adds the creator/admin with full permissions.
  • Creates a value stream and pipeline associated with the team, using application data from Deploy.
Analytics
  • Creates dashboards in Opensearch for the newly created loop.

Access and Permissions

The loop creator is granted the highest permissions for all resources in the integrated capabilities. Invited users are given only basic permissions by default when they join a loop. They can manually elevate their own permissions through the UI for any resource as needed.