Restricting issue types by default in the Settings does not work

Mikhail Ponomarev January 17, 2022

I created new issue type and added default restrictions to  certain roles in the settings. 

I expect the following: 

"For new issues, only allow these roles to view them by default."
But when I create new issue, it is created with No restrictions
Am I doing something wrong? How can I enforce this setting? 

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
Vishwas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 17, 2022

Hey @Mikhail Ponomarev 

Welcome to Atlassian Community !!

When you mean restrict issue type, how did you achieve this. Did you write any script in scriptrunner ?

Or you are referring to Issue security level ? Could you explain more ?

Based on these we can guide.

 

Regards,

Vishwas

Mikhail Ponomarev January 17, 2022

@Vishwas , no I am not using any script. I am using Settings only. So when I am in Project settings I simply click LOCK sign to make default restrictions. According to "Learn more" it shall work.

See screenshot:

Screenshot 2022-01-17 at 18.17.07.png

But when I create an issue of this type after settings are on, the created issue is not restricted. 

Vishwas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 17, 2022

Hi @Mikhail Ponomarev 

Got it, its Team Managed Project in Jira and you are using restrict issue type to users.

I did one round of testing it's working as they have mentioned in the doc.

So I configured for Issue type "Task" to only be visible to "Administrator"

While creating it showed me this by default "Restrict to" was filled to "Administrators"

TPM_Restrict_Issue_2.png

After issue created I switched to a user with member role in that project and i got this message.

TPM_Restrict_Issue.png

 

Please check if your red lock symbol is on and check with one of the users who are not in "Members" role.

 

Regards,

Vishwas

Mikhail Ponomarev January 18, 2022

@Vishwas thanks, but I see that on your screenshot you create issue by using big button Create on the top. I tried it and it works.

But if I create and issue on the board by using "+Create issue" then it doesn't work:

We almost always create issues on the board. Also not sure if the issue produced by Jira Automation will have the necessary restrictions....

Screenshot 2022-01-18 at 09.09.25.png

Vishwas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 18, 2022

Hey @Mikhail Ponomarev 

That's correct I have created using the "Create" button.

On the board while creating an issue restrictions are not applied, not sure why this behaviour(we may have to ask atlassian on this) but yes only summary can be given while creating issue on board and no other fields or restriction can be provided.

And in automation also you are right, restriction wont be applied.

Regards,

Vishwas

Mikhail Ponomarev January 18, 2022

How can I raise it with Atlassian? I thought this post makes it... 

Vishwas
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 18, 2022

Hey @Mikhail Ponomarev 

Sure let me guide you, basically this is Community. Atlassian Team might respond here but they may take some time.

But to get faster response from support create a ticket here https://support.atlassian.com/contact/#/ 

Regards,

Vishwas

Like Mikhail Ponomarev likes this
TAGS
AUG Leaders

Atlassian Community Events