Should we filter by status and resolution as well to be consistent with Changelog filtering?

We should. It can be quite confusing to see a number of issues left beside the 'View Issues' button and get another number of issues after clicking the button.

I agree, the filters should be consistent.

the filters should be consistent.

It's not that easy as it is not just status and resolution filtering.

The change log is also driven by a custom function, our default for it is

function custom_function_default_changelog_include_issue( $p_issue_id ) {
    $t_issue = bug_get( $p_issue_id );

    return( ( $t_issue->resolution >= config_get( 'bug_resolution_fixed_threshold' ) &&
        $t_issue->resolution < config_get( 'bug_resolution_not_fixed_threshold' ) &&
        $t_issue->status >= config_get( 'bug_resolved_status_threshold' ) ) );
}

The change log is also driven by a custom function

Should it be better if the custom function returned a filter for selecting the issues to include?
The logic showed there can be put into a filter.
I wonder if having a custom logic that could not fit into a filter, is really a use case.