You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I created new issue type and added default restrictions to certain roles in the settings.
I expect the following:
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.
@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.
But when I create an issue of this type after settings are on, the created issue is not restricted.
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"
After issue created I switched to a user with member role in that project and i got this message.
Please check if your red lock symbol is on and check with one of the users who are not in "Members" role.
@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....
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.