Workflow status properties being applied to all workflows inside a workflow scheme

Summary

Having a workflow scheme using more than one workflow and setting up properties for a status in one of the workflow will impact the status in every workflow.

Steps to Reproduce

1. Create a project and a workflow scheme with 2 workflows
2. Configure the workflows to have the same status
3. In one of the workflows add the permission properties to one of the status indicating the roles that can edit issues:

   jira.issue.editable = true
   jira.permission.edit.projectrole.1 = 10002
   jira.permission.edit.projectrole.2 = 10202
   

   Where 10002 and 10202 are the roles ids(Administrators and developers and status is To Do in this example).

4. Impersonate a user that is not in any of those roles.
5. The user won't be able to edit any issues in the To Do status in any issue types as this will be applied to all the workflows.

Expected Results

Only the issue types assigned to the workflow containing these properties should be affected.

Actual Results

The permission properties affect all the workflows and thus all the issue types in the project.

Notes

This should be happening for other properties.
Cloud documentation reference for properties.
This is important for customers that need different permissions depending on the issue type.

Workaround

Remove the properties from the workflow using them or have different statuses in each workflow.