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
  • Linking objects on diagram
  • Linking objects inside attributes
  1. Global features
  2. Diagram area

Linking objects

PreviousUpdating element detailsNextPlan browser

Last updated 8 months ago

Each component contain two handlers:

  • Source - it's a starting place or arrow indicating a relation of two components

  • Target - it's a destination place of components' relation

Linking objects on diagram

Linking objects is a subject of validation. Validation is based on possible connections that makes sense and are achievable in Jira configuration.

Below there is an example of possible and invalid connection.

It is reasonable to connect custom field (it's attributes like name or ID) inside Filter e.g. insdie used JQL. However it doesn't make sense or bring any value, to embed custom field attributes inside attributes of issue type.

Linking objects inside attributes

Linking objects on diagram, doesn't fully explains the realation between two components. To provide more details, you can optionally embed variables inside target compone. wut details.

  1. During a linking process, you will see similar popup message.

  2. Click on desired attribute of source component. It will copy to clipboard a variable indicating source attribute value.

  3. Paste value inside chosen attribute of linked target component

  1. Paste copied value inside chosen attribute of target component. The example linked attribute value will look like this:

JQL attribute:

${atlcloudjira_customfield.MyNewCustomField.id} = "Some value" and project = ABC ORDER BY Rank ASC
  1. Update component and save plan. Deployment team will now know exactly what was your true intention behind linking of two components.

Invalid connection.
Possible connection.
Copy source attribute variable into clipboard.
Now properties of source and target components are linked with variable