We are configuring a JPD with many pre-configured views for specific purposes. Is there any way to restrict who can edit those views?
In our use case, we have many people that need to be able to edit fields but not necessarily change which fields are visible. It's okay if they make their own view, but some views need to be defined and set.
Right now, any member can change view settings, so if they open one called "Ideas by Rank" and then apply a sort option, it no longer is by rank. This can be very confusing for our stakeholders.
You would go to administration, find your user, open the user and you will see the programs they have access to or have a license to. You would want to pick Jira product discovery.
hi @Yael Geffen . As @Adriana Domínguez Eguiarte says below, the user doesn't have a license for Jira Product Discovery so they can not be made an admin. A site admin needs to give this user a license before they can be made a Project Administrator or Creator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Yael Geffen A site admin needs to do the following. Go to:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think the problem is, that you have to previously assign this person a Jira Product Discovery license, as it is needed to give her a role as a Creator or Administrator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.