Summary

     When creating new JSM projects, a new permission scheme is always created instead of using the default permission scheme. In addition, the new permission scheme is some older/original version of the Default Permission Scheme. The purpose of naming it as Default Permission Scheme is to use the permission scheme when no other scheme is set.

Updated Default Permission Scheme

Newly created Project's Permission Scheme

Steps to Reproduce

1. Set a permission scheme as a Default Permission Scheme.
2. Edit the default permission scheme and save it.
3. Create a new JSM project (without setting the permission scheme) and review the permission scheme associated with it.
4. You will see that a new permission scheme is created for the project and it is different from the default permission scheme

Expected Results

• New JSM projects use the default permission scheme, if no permission scheme is selected during creation of the project

Actual Results

• A new permission scheme is created for the project and it is different from the default permission scheme 

Notes

• Raising a bug based on discussions in slack thread  #help-jsm-cloud

Workaround

In order to prevent this, 

• Select the permission scheme when creating the project

OR

• Update the permission scheme to a desired permission scheme after the project is created.