View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0008543mantisbtbugtrackerpublic2007-11-03 13:222014-10-05 19:05
Reporterherringm Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version1.1.0rc2 
Summary0008543: Resolved issues on "My View" page do not honor config value 'bug_resolved_status_threshold'
Description

Unless your configuration option sets 'closed' as the 'bug_resolved_status_threshold' the bugs listed in the "Resolved" box on the "My View" page is not complete.

For instance, if 'bug_resolved_status_threshold' is set to 'resolved' then this box should show bugs that match following standard status levels:
resolved
closed

Currently, only bugs that exactly match the level of 'bug_resolved_status_threshold' are displayed.

Steps To Reproduce
  1. Check your configuration status making sure 'Status where an issue is considered resolved' is set below closed
  2. Make sure you have at least one bug at and above the 'bug_resolved_status_threshold'
  3. View the "My View" page looking at the "Resolved box". Only the bugs at the 'bug_resolved_status_threshold' will be shown.
Tagspatch
Attached Files
partial_fix_8543.patch (1,291 bytes)    
Index: core/my_view_inc.php
===================================================================
--- core/my_view_inc.php	(revision 4716)
+++ core/my_view_inc.php	(working copy)
@@ -94,10 +94,25 @@
 	);
 	$url_link_parameters['reported'] = 'reporter_id=' . $t_current_user_id . '&hide_status=' . $t_hide_status_default;
 
+	$t_status_arr = explode_enum_string( config_get( 'status_enum_string' ) );
+	$t_available_statuses = array();
+	$t_desired_statuses = array();
+	foreach( $t_status_arr as $t_this_status ) {
+		$t_this_status_arr = explode_enum_arr( $t_this_status );
+		$t_available_statuses[] = $t_this_status_arr[0];
+	}
+
+	foreach( $t_available_statuses as $t_this_available_status ) {
+		if ( $t_this_available_status >= $t_bug_resolved_status_threshold ) {
+			$t_desired_statuses[] = $t_this_available_status;
+		}
+	}
+
 	$c_filter['resolved'] = array(
 		'show_category'		=> Array ( '0' => META_FILTER_ANY ),
 		'show_severity'		=> Array ( '0' => META_FILTER_ANY ),
-		'show_status'		=> Array ( '0' => $t_bug_resolved_status_threshold ),
+		'show_status'		=> $t_desired_statuses,
+		'_view_type'		=> 'advanced',
 		'highlight_changed'	=> $t_default_show_changed,
 		'reporter_id'		=> Array ( '0' => META_FILTER_ANY ),
 		'handler_id'		=> Array ( '0' => META_FILTER_ANY ),
partial_fix_8543.patch (1,291 bytes)   

Activities

herringm

herringm

2007-11-03 13:47

reporter   ~0016073

I have attached a partial patch built against the SVN trunk.

This patch updates the bugs listed in the "Resolved" box honoring the config variable 'bug_resolved_status_threshold'.

It does NOT however modify the two links generated in the "Resolved" box header. I do not know enough about the filter API at this time to properly generate the url parameters required for an advanced search query that passes multiple show statuses.
dib6

dib6

2008-03-27 08:22

reporter   ~0017475

I have encountered the same problem. I have created a custom status that should also be considered resolved and set 'bug_resolved_status_threshold' variable to proper value.

Now on My view page only bugs with my custom status set are displayed in "Resolved" box.