Good day, How can I specify that certain users can only create tickets for their own project? I have a user who only works in one project. However, when he clicks on ‘Create ticket’, he sees all projects. How can I prevent this? He should only see his own project and nothing else.
Are you referring to the Create button in the project UI + or you are referring to customers who uses the Portal UI to create issues for your JSM projects?
Please advise, so we can assist you better.
Best, Joseph Chung Yin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You just need to ensure that the user is not called out against the project(s) user and role assignments for Browse project permission. This means that they will not have access to the specific project(s).
Hope this helps.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jens Prokoph If your users still need to be able to see the tickets in the other projects but just not create, you can make sure the Create permission in the Permission Scheme for those projects is updated to exclude those users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The funny thing is that the user does not have any authorisations in the other projects.
He can neither access the portal nor see the tickets and the project is only displayed to him in this list.
I have just checked the creation authorisation again but found nothing here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will need to check to see which user group that specified user is in, then check to see if the group is assigned with any project rights (called out in the project's users and roles section of the project)
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is exactly my problem: The user is only in one group. The group is not stored anywhere in the project itself or in all projects except one and yet he is allowed to create tickets for all projects.
Therefore, I believe that it must be a global setting that I do not know yet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In that case, have to you each of your projects via Project settings >> project permissions configuration scheme to see if browse project and create issue permissions are granted?
Typically, it is granted for the project role named "Service Desk Team". Is the user associated with the Service Desk Team project role in the restricted projects?
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
unfortunately still the same. I have removed the authorisation that the ‘Service Desk Team’ can create and browse and the user can still create a ticket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have found the culprit. A ‘Reporter’ role was still stored in the authorisation. I completely overlooked this and didn't know its scope. After I removed this role, the list was gone and no more tickets could be created in other projects.
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.