Inconsistency in Scrum and Kanban boards ranking permissions

Summary

When ranking issues in both Scrum and Kanban, it is documented that you need both 'Schedule Issue' and 'Edit Issue' permissions. This works as expected in Scrum boards. However, in Kanban board issues can still be ranked with 'Schedule Issue' permission only (without the 'Edit Issue' permission).

Steps to Reproduce

1. In a software project, edit the permission scheme.
2. Set the 'Schedule Issue' permission to a user / group (e.g. Group_A)
3. Set the 'Edit issue' Permission to another group (e.g. Group_B)
4. Create Two boards, one Kanban and one Scrum.
5. Login with a user who does not have the 'Edit issue' Permission but has the 'Schedule Issue' Permission. (e.g. who belong to Group_A)
6. Try to rank the issues in the Scrum board, it works as expected, the ranking does not work and an error is returned that the user does not have the permission to edit the issues.
7. Switch to Kanban board and try to rank the issues. Issues are ranked without displaying any error message.

Expected Results

Issues will not be ranked in Kanban as the user does not have the 'Edit issue' permission similar to Scrum boards.

Actual Results

Issues are ranked in Kanban board. The rank column does reflect this change too.