nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update restriction field with automation

Matteo Gabanini

Hello everyone!

I want to update the restriction field (the one with the padlock) using the automation; the values to put it's the same of a custom field.

I tried to use the JSON format, but it seems that the name "issuerestriction" (I find this name invaked the createmeta API) is not correct.

I hope someone can help me

Accepted answers

All comments

Mikael Sandberg

Hi @Matteo Gabanini,

Welcome to Atlassian Community!

If you by restriction field means the one that sets the security on the issue then you are looking for the field called security level.

Matteo Gabanini

Hi @Mikael Sandberg

thanks for you answer!

No, I mean this field:

Screenshot 2024-06-17 104210.png

I want to set a specific role using an automation.

Thanks,

Matteo

Mikael Sandberg

That is the security level field, so the field name you are looking for is Security Level.

ヴァリエンテフロリアン_Florian Valiente_

@Mikael Sandberg

Not OP, but I am on a team-managed (next-gen) board, and when I try to set the Security Level field in the automation it gives me an error

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Security Level (security)

ヴァリエンテフロリアン_Florian Valiente_

@Matteo GabaniniJust sharing how I was able to do it on my side

Send Web Request
- Web Request URL: https://<your-instance-url>/rest/api/3/issue/{{issue.key}}
- HTTP Method: PUT
- Web Request body: Custom Data
- Custom Data
  - ```
  { 
    "fields": {
      "issuerestriction": {
        "projectrole": [
        {
          "restrictionValue": "<role-id>"
        },
        {
          "restrictionValue": "<other-role-id>"
        }
      ]}
    }
  }
```
- the role-id I got by querying an issue that had the restrictions set via UI
- Headers
  - Content-Type: Application/JSON
  - Authentication: Basic <your-email-address and api-token encoded in base64>

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud