@kongtiaowang can you review this PR for me? Thanks

@shonibare The "issue_tracker_close_all_issue: Close all Issues" permission seems unnecessary. In which specific scenarios is it used? If a user has only this permission, they cannot access the module. However, when combined with any of the "Issue Tracker: See/Edit/Comment and Close" permissions, the user gains full access. These three permissions together already include the ability to close issues independently.

@Shen, the issue_tracker_close_all_issue permission is dependent and does not grant access to the module unless the user also has a permission with "See" issues. The issue_tracker_own_issue permission allows users to close issues they have created and provides access to the module.

The issue_tracker_all_issue and issue_tracker_site_issue permissions alone do not allow users to close issues unless they also have the issue_tracker_close_all_issue or issue_tracker_close_site_issue permission. If a user is granted only issue_tracker_all_issue and/or issue_tracker_site_issue, the "Close" option will not appear in the Status filter/field on the Edit Issue page.

@shonibare this has conflicts, can you rebase it?

I am not going to block on this because this works and has been tested, but in the future I think a better design would be to move the permission checking logic into the IssueRow and implemented AccessibleResource interface, rather than modifying the SQL query for permission checking.