I've returned from an absence and my service management project is suddenly giving me permission scheme errors for not allowing Portal Customers to have "Move" permissions.
I have "Move" restricted on my project for several reasons and really do not want to enable it. We do not want issues to be moved off of the project or workflow steps/approvals to be skipped with it.
Is there any reason why a Portal Customer could possibly need it that would break some new update or Core feature? Anyone know of a recent update that affects this?
In addition to what @Eugenio Onofre provided - In general, portal customers would never be granted with the MOVE issue permission against projects. It is important that your users (agents) who are a member of Service Team Members role should have this permission if and only if they are the same agents for multiple projects in your env.
Keep in mind that, agents may be different within multiple JSM projects. (Example - Agents for ITSM JSM project versus Agents for HR JSM project)
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
This is exactly why the pop- up threw me so much - saying that "Service Project Customer - Portal Access" must be assigned the Move Issues permission (not recommended, but must be assigned) seems out to left field. It made me wonder if some major update had happened for portal customers.
@Eugenio Onofre Unless I am misunderstanding here, it is asking me to fix the security scheme by assigning the permission of "move" to "Service Project Customer - Portal Access", which to me seems very strange. It is not currently enabled. I'm a little confused by the end of your last sentence.
...eturns true if any content is returned for the webResponse.body.data.first s...