Is it possible to disable create issue button or put a restriction where in agents can't create request on this option. So that they will be directed to customer portal.
Any suggestions will be highly appreciated!
Hi @Darren Laurel You can remove the ability to create issues by going to Permissions Schemes and selecting the permissions Schemes that you are using then choose remove project role
if you are removed permission, never create any issue. because i have checked and confirm.
it's not good Idea.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Darren Laurel you can remove create permissions from each project's settings. In practice, I have done this at my organization to only allow a very small group of users to create tickets in the 'Agent View' where all other users must use the portal.
In theory, you could remove the permission from every project. The Create button would still appear, but I'm not entirely sure what would happen if you clicked the 'Create' button without the permissions to create any tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community. To supplement what Mathew stated, when a "agent" (who have Create Issue permission revoked against a project), when he/she clicks on the "Create" button, they will not be able to see the specific project listed in the project choice option dropdown in the Create pop-up screen.
Hope this also helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Disabling the Create button via the Permission Scheme works, but. . . this prevents your JSM agents from Moving and, I believe, Cloning issues. The inability to move issues within a project was a deal breaker for us. I welcome a better solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This solution seems cleaner so far, assuming you have ScriptRunner: https://docs.adaptavist.com/sr4js/latest/features/behaviours/behaviours-examples/restricting-issue-types
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Disregard. Without more sophisticated logic, this solution actually removes the Issue Type value from existing issues, which prevents them from being edited.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you remove the "Browse Projects" and "Create Issues" permissions then this is what the user will see when the "Create" button is pressed. Removing the button is really just a quality-of-life issue and I suppose these users will just have to live with it. My use case is applying this permission scheme for users that only need to reply and update issues, and never create one.
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.