Requesters – Members of this group require all of the permissions that are assigned to the default Reporter role except for Read Issue.They should have the following permissions: To support this scenario, each of these groups (as a collection of users) is assigned a role that grants the appropriate level of access. These names are used intentionally to avoid confusion. Note that the names that are assigned to these groups are different from the names that are assigned to the default roles in YouTrack. This list includes, for example, the head of the accounting team or a company lawyer. These are people who can read and update any issue, if necessary. Members of this team are expected to be in the list of Assignees. Executors should be able to read and update any issue. These are the members of the accounting team who process payment requests. These people should be able to create requests, but should only be able to read the issues that they created themselves. This is the collection of employees who are allowed to request payments from the accounting team. The most straightforward way to handle this scenario is to use the permission scheme in YouTrack.įirst, define the groups of agents who participate in these issues: Therefore, each issue must visible only to the reporter and the members of the accounting team.įor this scenario, we have two different techniques to tackle the problem. The payment details and invoice are considered to be sensitive data. Various employees create issues that contain the details of the requested payment and a copy of the invoice. They use YouTrack as a means of transparent communication with other departments. The team processes payments for business trips, advertising, conferences, and the like. Imagine that you have an accounting team whose members help other employees pay work-related invoices. Specifically, we’ll show you how to restrict visibility so that each issue can be read by a very limited set of people and manage visibility independently for each issue in a project. This post is devoted to visibility restrictions. With this article, we begin a series of blog posts that demonstrate how to support specific processes in YouTrack with the help of workflows.
0 Comments
Leave a Reply. |