User can't see all groups when sharing dashboard

[Claire Berry]

A user has reported an issue where he is unable to share a dashboard with a particular group. The User Directory which his account is from is configured with Microsoft AD, and the group he is looking to share with is also from this directory. When I try to share a dashboard, as an admin, I can see this group as an option. But his list of groups that he can see is far more limited. He has Browse Users permissions.

From what I can tell, it looks like he can only see groups that he is in. Is this expected behaviour? And is there a way to change this so users are able to view and select all groups when sharing a dashboard?

[Yogesh Mude]

Hi @Marzi Goodarzian

Please follow the steps..

1. Copy and Create the field configuration.

2. Select the Field which you want to make required, do it.

3. Copy and create the Field configuration scheme and add the created Filed configuration in step 1.

4. Associate this Field configuration scheme with the project in which you want that field to be required.

please have a look at this article for detail information.

[Alexey Matveev]

Hello,

You should define two field configuration schemes. In one of the field configuration schemes the field will be required, and in the other one the field will not be require. Then you attach the necessary field configuration scheme to each project. In this case you will not be able to create an issue, if you do not provide a value for the field. You can find more info here:

https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

If you need to define a field to be required for just a single transaction screen, then you would need a plugin for it. For example, you can read this KB:

https://confluence.atlassian.com/jirakb/how-to-make-jira-applications-fields-required-in-a-workflow-transition-691011903.html

[Ollie Guan]

The configuration of the screen is correct and you should adjust the configuration of the field

[Deleted user]

Hi @Marzi Goodarzian,

My suggestion would be to use a field configuration scheme for each project; one scheme can have the particular field set as required, and the other can have the same field set as optional. 

Hope this helps