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
Dear community members,
can you please advise me, how to configure user to:
Thanks in advance!
Hi @Timofey Prokhorov , thanks for your question.
1) You can control where users can create issues by the Permission scheme. The minimum permission is 'Browse project' and 'Create issues'. Typically other permissions are needed, like 'schedule issues' to set an end date, and also 'edit issues'.
2) To limit who can see issues, you can use an Issue Security Scheme.
In the Issue Security scheme, you have the possibility to specify different levels of access. This works a bit like it does in a notification scheme where you can say, the people who can see the issue are the reporter and a project role like members.
The typical use case for this is a HR setting, where most of the team should be able to see most issues, but there will be some types of subjects where the visibility should be limited.
In the scheme, you can create levels, one which is open and where you can give the access to view and work on the issues to most members of the project.
Then, you can set another security level that is more closed, let's say just for HR managers.
You can also define the default issue security level, so that most issues, when they are opened, have the more open level set so that there are more people available to work on the issues.
You could have an Automation, for example, for the type of issue, let's say someone opens an issue in the HR project to say they are resigning, you could set an automation for the type of issue to set the security level to Private or Limited, so that only a smaller group of people can see the issue.
I have included a link to the documentation for how to get started. If you have other questions, please reply here and someone will try to help.
Welcome to the Atlassian Community!
To prevent people creating things in the wrong project, remove their permission to "create issue" in the projects you want to protect.
To get issues that are only visible to the reporter, you will need to create an "issue security scheme" which includes the rule "reporter can see issue" on at least one level, then set up an automation or script that sets that security level on every issue.