JIRA Issue Field option with project defined in scope shows in all projects

Suppose there is a custom JIRA Issue Field defined in the connect app.

"jiraIssueFields": [
      {
        "description": {
          "value": "My Field"
        },
        "type": "single_select",
        "name": {
          "value": "My Field"
        },
        "key": "my-issue-field"
      }
    ]

I have added several options to this field like this:

{
  "id": 1,
  "value": "My option 1",
  "config": {
    "scope": {
      "projects": [10001]
    }
}

According to the documentation, especially according to the IssueFieldOptionConfiguration link inside this page:

this “Defines the projects that the option is available in”.

But this doesn’t work, the option is available in all projects anyway.

Am I doing something wrong?
Thank you for any hint.
Ales

And another question: there are two similar properties in the scope: projects and projects2. What is the difference between them? Documentation is silent about this unfortunately :frowning:

"scope": {
      "projects": [],
      "projects2": []
}

Thanks for any hint.
Ales

Hi @KahanekAles,

The documentation actually says that that the projects property is deprecated (you’ll see it if you drill down into the IssueFieldOptionScopeBean definition). Therefore it should not be used. The correct way to mark your option as available only in project 10001 would be:

{
  "id": 1,
  "value": "My option 1",
  "config": {
    "scope": {
      "projects2": [
         { "id": 10001 }
      ]
    }
}

Hope this helps :slight_smile: