Is there anyway to just remove the permission to "Create linked issues" but still allows access to Link 2 issues together. or can that option be just hidden from the More dropdown list? We don't use that functionality and has caused issues. We only need to link existing tickets together and not create linked issues.
Hi @Jason Michaud To create a linked issues you should have Create issue and Link issue permission for that respective project. If you remove Create issue permission you won't be able to create issue but can link existing issue.
Try to remove create issue permission and allow only Link Issue permission.
Thanks
V.Y
Thank you for your input.
Yes- but this is a Service Desk project - so everyone needs to be able to create issues. It is this permission which I wish was broken into 2. We don't need the 2nd option of create linked issues. There is no need for using it for my organization. So I'd rather block access.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can limit what Project(s) a user can create Issues in using Project Permissions. The Create and Link permissions are separate...
See more about what each permissions does on this page.
If you're looking to hide the actual option, I don't believe there's a native way of doing this.
It might be possible with a scripting App though. For example, you could use a Script Fragment with Scriptrunner to hide it assuming you can find the appropriate Issue Operation from the API list.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for you reply, Yes - but this is a service desk project where I need everyone to be able to create issues. It is the Link Issue permission that I wish was separated into 2 - 1) ability to link issues and 2) Ability to create linked issues. The #2 option is what I want to block from being used. But I would rather not create anything customized that has to be manually supported.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If it's a Service Management Project, does every user need the option to create Issues from the internal view? Or just the portal?
There's a difference here between...
Ste
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.