# atlcloudjira\_screen\_scheme (Resource)

## Example Usage

```terraform
import {
  to = atlcloudjira_screen_scheme.SampleScreenSchemeResource
  id = 10081
}

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

# __generated__ by Terraform from "10081"
resource "atlcloudjira_screen_scheme" "SampleScreenSchemeResource" {
  description = "Sample description"
  name        = "Sample Screen Scheme AA"
  screens = {
    create  = 10127
    default = 10125
    edit    = null
    view    = 10134
  }
}
```

## Schema

### Required

* `name` (String) The name of the screen scheme.
* `screens` (Attributes) The IDs of the screens for the screen types of the screen scheme. Only screens used in classic projects are accepted. (see [below for nested schema](https://docs.silessian.com/planapply-for-jira-cloud/terraform-provider-for-jira-cloud/terraform-provider-for-jira-cloud/broken-reference))

### Optional

* `description` (String) The description of the screen scheme.

### Read-Only

* `id` (Number) The ID of the screen scheme.
* `last_updated` (String) Timestamp of the last Terraform update of the project component.

### Nested Schema for `screens`

Required:

* `default` (Number) Default screen ID associated used at issue browsing.

Optional:

* `create` (Number) Screen ID associated with Create issue action
* `edit` (Number) Screen ID associated with Edit issue action
* `view` (Number) Screen ID associated with View issue action


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.silessian.com/planapply-for-jira-cloud/terraform-provider-for-jira-cloud/terraform-provider-for-jira-cloud/atlcloudjira_screen_scheme-resource.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.