Default security level is cleared when creating issues via Script Runner

Jira Development Jira Data Center
1

Hi there,

When creating issues using the Jira API via Script Runner, the default security level is not set under the conditions below if the security level is not explicitly included in the input parameters:

  • A create Issue screen includes the Security Level field, and the executing user has permission to set the security level.

Note: If the Security Level field is removed from the Create screen, the default security level is applied.

To resolve this, would the only options be either to remove the field from the Create screen or to explicitly include the security level in the input parameters?

Thank you.

2 Likes
2

To clarify

  1. You have an issue which does not have the Security Level field on the create screen
  2. You do have a Security Scheme and default security level set up. And it works when you create an issue with the UI
  3. You create an issue with the REST API without passing in a Security Level value
  4. The issue is created without the default security level set

Is that all correct?

Does this also happen if you use a different tool from ScriptRunner to create an issue?

3

Hi Matt,
Thank you for your reply.

  1. You have an issue which does not have the Security Level field on the create screen
    → No, the issue occurs when the Security Level field is present on the create screen.

  2. You do have a Security Scheme and default security level set up. And it works when you create an issue with the UI
    → Yes, the Security Level is properly configured, and it works fine when creating an issue via the UI.

  3. You create an issue with the REST API without passing in a Security Level value
    The issue is created without the default security level set
    → We have not tested this behavior with the REST API yet.

  4. Does this also happen if you use a different tool from ScriptRunner to create an issue?
    → We have not tested it with any tool other than ScriptRunner yet.

4

Thanks for the clarification. Two more questions:

  1. Is this Data Center or Cloud?

  2. Does the user creating the issue have the Set Issue Security permission for the project?

5

Thank you for asking in such detail.

  1. Is this Data Center or Cloud?
    →It’s Data Center.
  2. Does the user creating the issue have the Set Issue Security permission for the project?
    →Yes, the user has that.
6

Got it, I think. I expect that if the user creating the issue does not have permission to set the security level, then the expected default security level is used. But because the user does have the ability to set the security level, then it is expected that the security level is passed in to the REST API call.

Now, how are you creating issues using the REST API with ScriptRunner? And why not use the internal Jira Java API directly?

7

Hi Matt,
We are not using the REST API; instead, we are using the Jira Java API.
I posted about an issue occurring with the Jira Java API.
Thanks,

8

Wow, I really should read the original question, sorry
But is this in a post function context or a separate script console?
Are you able to post a snippet of the Groovy script that created an issue