Jira Environment Mapping

Integrate Tugboat with Jira using the GitHub for Jira plugin to map your deployment environments. This ensures that deployments from Tugboat (and other environments) are displayed with the correct labels in Jira, making it easier to track where your code is running.

Prerequisites

  • A GitHub repository with environments set up (e.g., Dev, Test, Tugboat, Production Host).
  • Jira Cloud instance with the GitHub for Jira app installed and connected to your GitHub organization.

Configure Environment Mapping

By default, Jira may show deployments as “unmapped” unless you configure environment mapping. To fix this:

  1. Add a .jira/config.yml file to your repository root:

    deployments:
  environmentMapping:
    development:
      - "Dev"
    testing:
      - "Tugboat"
    staging:
      - "Test"
    production:
      - "Production Host"
    • Deployments to Dev will show as Development in Jira.
    • Deployments to Tugboat will show as Testing in Jira.
    • Deployments to Test will show as Staging in Jira.
    • Deployments to Production Host will show as Production in Jira.

    Tip: Adjust the mapping to fit your workflow. For example, if you consider Tugboat a staging environment, map it under staging instead of testing.

  2. Result in Jira

    Once configured, deployments will appear in Jira under the correct environment labels. For example, a deployment to Tugboat will show up as “Testing” in Jira.

    Example screenshot of deployment mapping in Jira Example screenshot of deployment mapping in Jira

References