atlcloudjira_issue_type_screen_scheme (Resource)

Example Usage

import {
  to = atlcloudjira_issue_type_screen_scheme.SampleIssueTypeScreenScheme
  id = 10051
}

# __generated__ by Terraform
# Please review these resources and move them into your main configuration files.

# __generated__ by Terraform from "10051"
resource "atlcloudjira_issue_type_screen_scheme" "SampleIssueTypeScreenScheme" {
  name        = "Sample Issue Type Screen Scheme"
  description = "Lorem ipsum."
  issue_type_mappings = [
    {
      issue_type_id    = "10001"
      screen_scheme_id = 10028
    },
    {
      issue_type_id    = "10004"
      screen_scheme_id = 10047
    },
    {
      issue_type_id    = "10009"
      screen_scheme_id = 10042
    },
    {
      issue_type_id    = "default"
      screen_scheme_id = 10047
    },
  ]
  replace_with = 10010 //required only when destroying the resource. Is set to null after import by default
}

Schema

Required

• issue_type_mappings (Attributes Set) The list of issue type to screen scheme mappings. (see below for nested schema)

• name (String) The name of the issue type screen scheme.

Optional

• description (String) The description of the issue type screen scheme.

• replace_with (Number) Helper attribute. Replaces current issue type screen scheme with new one in associated projects, when performing delete operation.

Read-Only

• associated_projects (Set of Number) Helper attribute. Stores in state a list of associated projects.

• id (Number) The ID of the issue type screen scheme.

• last_updated (String) Timestamp of the last Terraform update of the project component.

Nested Schema for issue_type_mappings

Required:

• issue_type_id (String) The ID of the issue type or default. Only issue types used in classic projects are accepted. An entry for default must be provided and defines the mapping for all issue types without a screen scheme.

• screen_scheme_id (Number) The ID of the screen scheme. Only screen schemes used in classic projects are accepted.