View Issue Details

IDProjectCategoryView StatusLast Update
0022404mantisbtfilterspublic2017-10-25 08:51
ReportervboctorAssigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version2.0.1 
Target VersionFixed in Version 
Summary0022404: View Issues in Changelog doesn't filter by status
Description

When you click View Issues button next to a version in Changelog, it only filters on fixed_in_version, hence, if an issue is open but has fixed_in_version set to the version number, then it will show in the filter.

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

TagsNo tags attached.

Relationships

has duplicate 0023322 closedatrol Change log doesn't show all issues fixed in the selected version 
related to 0023311 closedatrol "View issues" on changelog page does not show closed issues 

Activities

atrol

atrol

2017-02-22 02:22

developer   ~0055734

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.

dregad

dregad

2017-02-22 02:58

developer   ~0055735

I agree, the filters should be consistent.

atrol

atrol

2017-09-06 08:15

developer   ~0057623

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' ) ) );
}
cproensa

cproensa

2017-10-22 06:13

developer   ~0058019

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.

Issue History

Date Modified Username Field Change
2017-02-21 22:50 vboctor New Issue
2017-02-22 02:22 atrol Note Added: 0055734
2017-02-22 02:58 dregad Note Added: 0055735
2017-09-05 09:05 atrol Relationship added related to 0023311
2017-09-06 08:15 atrol Note Added: 0057623
2017-09-06 08:15 atrol Relationship added related to 0023322
2017-09-06 09:26 atrol Relationship replaced has duplicate 0023322
2017-10-22 06:13 cproensa Note Added: 0058019