How to make certain Issues visible only to a specific user group in YouTrack

In our YouTrack project all issues are historically visible to "all users" which is also the group with the same name that shipped with YouTrack.

Now we are adding new users with restricted permissions and they should only see a small part of the issues. They should start seeing no issues at all, and then single issues (old issues and new issues) should selectively made visible to them.

I tried different ways to make this happen, but without success.

1) If I create a group for them "restricted group" - then I can give this group permission to view issues. And then they can see all issues, and if I uncheck the "view issues" privelege checkbox, then they cannot see any issue at all. This does not help me, as they either see all issues or none.

2) I tried to change the "issues is visible to" field in a single issue and set it to "restricted group". But YouTrack won't let me, only "all users" or "project XY Assignees" can be selected here. Edit: this is still true, after I add myself to "restricted group", see Alex.V's answer to this question

So I deleted the group "restricted group" and tried to work with "assignees":

3) I choose an issue and set its visibility to "My Project Assignees". And then I add a user to the "My Projects Assignees" group. But now the user can see ALL the issues in that project. In the group settings I find out, that the checkbox "Read issues" in the definition of this group's role "Developer" can be unchecked, and this changes visibility. But again for all Issues! And it does not matter If I set the visibility for the issue to "My Project Assignees" or to "All users" - now the user can see no issues at all, after unchecking the checkbox.

This is YouTrack 4.2.2 (build #6029 [23-May-2013 18:30]

Please show me a way to selectively make issues visible to a group of users and invisible again. I know it is possibly quite simple, so what is my mistake?
11 comments
Comment actions Permalink
No matter what I tried, I could only always make either all or no issues of a project visible to a certain user. With one exception: Users can see their own Issues that they created, in a certain configuration, and not the other issues in the same project. But this does not really help, as long as I am not able to change this field as an admin. So is there a way for me as an admin to change the filed that affects this visibility "issue created by"?
0
Comment actions Permalink
Something that I noticed: maybe the "Assignees Group" configuration is broken in our YouTrack instance. When I create a new project it does not have the "XY Assignees" group anymore. Maybe this is related to the problem?
0
Comment actions Permalink
I tried a different approach: adding the user as a watcher. But it did not help. Although the user can see his own created issues in a project, she cannot see the issues she is 'watching', after I add her as a watcher.
0
Comment actions Permalink
Hi,
Seems I've answered this on stackoverflow, but if you have further questions, we can really proceed here.
0
Comment actions Permalink
Please not that a user should posses 'Update Issue' permission in order to change the visibility


Thank you, I checked, and I do posses 'Update Issue' permissions. In fact I can change the visibility with teh dropdown and set it to one of the groups, or I can set it back to "All Users".
0
Comment actions Permalink
In the meantime I was able to understand how the view permissions work.

The dropdown box at the top of the issue page acts only as a filter and you can only EXCLUDE users with this dropdown box that could already see the issue when visibility was still set to "all users".


So I think to acomplish what I want I will have to change all issues' visibility to let's say "admin1 group" and later switch only some of them back to "all users" so everybody can see those.
0
Comment actions Permalink
In fact 'Visible for' means that only members of this group and the reporter will be able to see the issue (or comment, if visibility is restricted for the individual comment).

This is one of possible solutions. In case you decide to proceed with it, please mind that you can set visibility for multiple issues at once using YouTrack command window: mark several issue, press ctrl+alt+j. The command would be visible to group_name.
0
Comment actions Permalink
Yes, this is a good solution and we will stick with it for now. I already did a test install of V5, maybe there will be more options with visibility.

I am also going to update the stackexchange crosspost when it is all set.

The mass manipulation using the command window is great, I already discovered it and that's how we could put this solution to production very fast.

I have another question now: When a new issue is crreated, it is visible to evrybody by default and It's easy to forget to change the group. Can this be changed, so the default visibility is another group?

Thank you.
0
Comment actions Permalink
YouTrack 5 does not any means in terms of visibility options.

It's possible to create a simple workflow rule that will automatically set visibility group for newly created issues. Do you need assistance on this?
0
Comment actions Permalink
I would appreciate if you helped creating the workflow rule. I managed to connect the workflow editor and I believe it has to be a stateless rule?

The rule should be applied as early as possible to a new issue. No need for a message, it can silentliy apply the visibility filter for the new issues ath teh moment it enters draft state.

But wait, when a user not in that admin group, nothing should happen - it has to stay visible for everybody.

Edit: I removed my suggestion here. Wrong code should be eliminated :)
0
Comment actions Permalink
Hello mit,

I've corrected the syntax a little bit:
rule When user is member of "admin1 group" set visibility of draft issue to that group 
 
when !isReported() { 
  var checkGroup = {group: admin1 group}; 
  if (!loggedInUser.isInGroup(checkGroup.name)) { 
    permittedGroup = checkGroup; 
  } 
}

defaultVisibilityGroup.zip (2.2KB)
0

Please sign in to leave a comment.