Silessian
PlanApply for Jira Cloud
PlanApply for Jira Cloud
  • Introduction
    • 🚀About PlanApply for Jira
    • 🛸Features overview
    • 📚Use cases
    • 💿Data structure and processing
    • 💡Workflow
  • Configuration
    • Get started - app configuration
      • 1. Client configuration
      • 2. Submission and provider configuration
      • 3. Remote repositories
  • Global features
    • Designer - getting started
    • 📐Designer
      • Toolbox section
        • Toolbox
        • Templates
        • Import / Export
        • Plan details
        • Submission
        • Collaboration
    • Diagram area
      • Diagram actions
      • Importing objects
      • Adding new elements
      • Updating element details
      • Linking objects
    • 🌏Plan browser
  • Admin features
    • Workspaces
    • Remote repositories
    • Plan browser
    • Terraform console
      • Workspace tab
      • Toolbox tab
      • Terraform tab
        • Generate config
        • Plan
        • Apply
      • Transform tab
    • AI Assistant
    • Execution logs
  • Terraform Provider for Jira Cloud
    • Terraform provider for Jira cloud
      • jira-cloud Provider
      • atlcloudjira_groups (Data Source)
      • atlcloudjira_issues (Data Source)
      • atlcloudjira_users (Data Source)
      • atlcloudjira_customfield (Resource)
      • atlcloudjira_dashboard (Resource)
      • atlcloudjira_field_configuration_scheme (Resource)
      • atlcloudjira_field_configuration (Resource)
      • atlcloudjira_filter (Resource)
      • atlcloudjira_issue_link_type (Resource)
      • atlcloudjira_issue_type_scheme (Resource)
      • atlcloudjira_issue_security_scheme (Resource)
      • atlcloudjira_issue_type_screen_scheme (Resource)
      • atlcloudjira_issue_type (Resource)
      • atlcloudjira_notification_scheme (Resource)
      • atlcloudjira_priority_sequence (Resource)
      • atlcloudjira_permission_scheme (Resource)
      • atlcloudjira_priority (Resource)
      • atlcloudjira_project_component (Resource)
      • atlcloudjira_project_role (Resource)
      • atlcloudjira_project (Resource)
      • atlcloudjira_screen_scheme (Resource)
      • atlcloudjira_screen (Resource)
      • atlcloudjira_status (Resource)
      • atlcloudjira_workflow_scheme (Resource)
      • atlcloudjira_workflow (Resource)
  • Support
    • How to report a bug?
  • 🔓Security statement
Powered by GitBook
On this page
  1. Admin features

Workspaces

Workspace browser

Workspace page accessible to site admins, allows to manage workspaces.

What is a workspace?

  • Workspace is an data structure that contains files (terraform scripts, json files, etc.).

  • Workspace can have plan associated with it. With this, plan data is automatically transferred into workspace and saved as a JSON file.

  • Workspaces can also be connected with remote Git repositories.

  • Terraform and Git operations processed externally are performed against entire workspaces. They are treated as virtual "folders" containing files.

  • Workspaces can be selected. Terraform console and Execution logs pages operates on selected workspaces.

  1. In this box you can enter a name of new workspace and create it with "New workspace" button. After that, the list will refresh and you will see new workspaces appended. Workspaces are empty when created. Name of the workspace is presented in the list.

  2. Workspace list contains all workspaces existing in given instance.

  3. Select workspace operation marks it as a currently selected workspace. This is important for Terraform console and Execution logs page, as they operate on selected workspace data. When workspace is selected, green icon appears before workspace name.

  4. You can rename workspace, by typing new name in dialog form and saving it.

  5. You can view files stored in given workspace. Files are stored in Atlassian Forge app storage.

  6. You can delete workspace and all it's files. Confirm the operation in dialog.

Deleting a workspace will remove all files stored inside it!

If you delete a workspace that contains associated plan, it will not remove the plan! You will see in plan browser, that workspace association was removed.

  1. Label "Remote / Not connected" present information is given workspace is associated with remote Git repository. New workspaces are not connected by default.

  2. This workspace description shows:

    1. Generic workspace ID that helps to debug and identify given workspace. Workspace ID can be present on plan browser if it's associated with plan

    2. Associated plan ID is present if workspace was created from plan browser. Otherwise, it will be set to None.

PreviousPlan browserNextRemote repositories

Last updated 9 months ago