New created User groups not visible in other screens.

[Kurt Callebaut]

Hi, i created a user group "Productie en planning" and want to give them users of this group access to jira and a specific dashboard. But it seems the new craeted usergroup is not visible in other screens.

So i gave them access to Jira product and i go to "create dashboard" to give this group access to a new dashboard. But i don't see the group in the dropdown.

does anyone know what goes wrong here ?

(The translations is another issues, sometimes we have English, sometimes Dutch, my apologies for the screenshots.)

[Tarun Sapra]

Hello @Kurt Callebaut 

You have to be part of the group, only then you can share the filter/dashboard with that group.

Hence the group which you have created, you need to be part of that group and only then you can share board/filters with that group.

Currently your requirement is an open request

https://jira.atlassian.com/browse/JRASERVER-15900

As an Admin I want the ability to share the visibility of a filter with Groups and Roles that I am not a member of

[Natalie Gashkova]

Thank you so much! 

Jeez, who created this Super-logic(((

[Kurt Callebaut]

Well, it seems that an administrator cannot configure filters and dashboard for other groups, unless you put him into the group. With result that the filters are not correct anymore because they show also the issues from admins.

Like MS windows an admin should not be in all groups, but he should have rights to assign groups to features. 

how can you configure for other people ?

Not logical at all.

[Kurt Callebaut]

Thank you Tarun,

It makes user groups useless, because all data for that group also includes the data from admins and that is not what you want to show users from a group with limited restrictions.

So my question to atlassian :

How can an admin make a filter for a user- group only showing their own issues ???

(not admin issues.) Seems pretty basic functionality for an administrator.

i'm pretty stuck in my configuration/setup for our company. 

Thx,

Kurt

[Tarun Sapra]

Hello @Kurt Callebaut 

"It makes user groups useless, because all data for that group also includes the data from admins and that is not what you want to show users from a group with limited restrictions."

This is not the exact case, because I understand from your comment 

"How can an admin make a filter for a user- group only showing their own issues ???"

You can create a group for users with restricted access and share with them only their issues, you can share the filter with the group. The only prerequisite being you have to add a single admin to the group so that the admin can share the newly created filter with the group having users with restricted access.

[Kurt Callebaut]

i think there is some miscommunication. :) 

Try next steps...

Make a new group "restricted users". (not containing admin)

Login as admin.

Try to make a filter where the filter contains   (group = "restricted users") to show only the issues from group "restricted users" and admin issues are not part of it.

-> the dropdown does not show the new group "restricted users" for the filter because admin is not a member of the group.

You cannot select that group for the where clauses for a filter if admin is not added to that group.

So if you add admin to the group "restricted users" (which is weird.), Then you can select that group in your filters, But you also see the admin issues. :) and that is not what we want for our filters.

if you try step by step you'll see its not logical.

[Tarun Sapra]

Hello @Kurt Callebaut 

I completely understand your remark

 the dropdown does not show the new group "restricted users" for the filter because admin is not a member of the group.

because admin is not part of that group.

But here's the catch, you have said

So if you add admin to the group "restricted users" (which is weird.), Then you can select that group in your filters, But you also see the admin issues. :) and that is not what we want for our filters.

Why will you see "admin issues"? Can you share the JQL filter which you are using or are you using assignee in "members()" something like that, in that case you add the criteria assginee not in "membersOf("admin_Group") so in this way you see the issues belonging to restricted group minus the issues belonging to admin group.

[Kurt Callebaut]

Hi, thx again. :)

Why will you see "admin issues"? 

- Because i'm admin for the tool and i also report issues like all other users. 

- i understand you can add admin to the group and exclude admin in the query, but its not the way to go for 30 filters. Admin should have access to all data and configurations without being a member and without afterwards fixing it by modifying the queries.

Seems there is a mix-up or unwanted relation between rights to configure and parameters to retrieve data.

i'ts like a bankaccount manager configuring my bankaccount and i can view his money also.  lol :D maybe in this case i will like it.  ;)

[Tarun Sapra]

Hello @Kurt Callebaut 

I completely understand your pain on this, but this is how it is right now, an admin has to be part of the group if he wants to share the filter with a particular group. I have also faced this issue myself, so can understand.

Let's hope, Atlassian implements this soon :) - https://jira.atlassian.com/browse/JRASERVER-15900

If you feel my answers helped, please accept/upvote so that other users are also helped. thanks.

[Kurt Callebaut]

same for creating filters to select issues by group.