View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0013707 | mantisbt | customization | public | 2011-12-31 20:16 | 2014-09-23 18:05 |
Reporter | JanHegewald | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
OS | Windows | OS Version | XP | ||
Product Version | 1.2.8 | ||||
Target Version | 1.2.9 | Fixed in Version | 1.2.9 | ||
Summary | 0013707: Custom resolutions not displayed cross-project | ||||
Description | Assuming issue "1" in project "A" has a custom resolution "testing" defined as described under Additional Information below, the resolution string is displayed as @X@ in the view issues page :
Same behavior in view issue details page, looking at another issue "2" defined in project "B", relationship to issue 1 | ||||
Additional Information | Sample definition for custom resolution: resolution_enum_string = '10:open,15:review,20:fixed,30:reopened,40:unable to duplicate,50:not fixable,60:duplicate,70:not a bug,80:suspended,90:wont fix'; | ||||
Tags | No tags attached. | ||||
Attached Files | 0001-Fix-cross-project-display-of-custom-resolution-codes.patch (2,100 bytes)
From b7644019f3a6321dba99afe9f9e6b59c44e61ee6 Mon Sep 17 00:00:00 2001 From: Damien Regad <damien.regad@merckgroup.com> Date: Sun, 1 Jan 2012 02:19:55 +0100 Subject: [PATCH] Fix cross-project display of custom resolution codes When a custom resolution is defined in a different project, its code was displayed as @X@ instead of the corresponding string in the resolution column, as well as when hovering over the status in the view issues page. Fixes #13707 --- core/columns_api.php | 9 +++++++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/core/columns_api.php b/core/columns_api.php index 96e94d6..dbba861 100644 --- a/core/columns_api.php +++ b/core/columns_api.php @@ -1115,7 +1115,9 @@ function print_column_reproducibility( $p_bug, $p_columns_target = COLUMNS_TARGE * @access public */ function print_column_resolution( $p_bug, $p_columns_target = COLUMNS_TARGET_VIEW_PAGE ) { - echo '<td class="center">', get_enum_element( 'resolution', $p_bug->resolution ), '</td>'; + echo '<td class="center">', + get_enum_element( 'resolution', $p_bug->resolution, auth_get_current_user_id(), $p_bug->project_id ), + '</td>'; } /** @@ -1127,7 +1129,10 @@ function print_column_resolution( $p_bug, $p_columns_target = COLUMNS_TARGET_VIE */ function print_column_status( $p_bug, $p_columns_target = COLUMNS_TARGET_VIEW_PAGE ) { echo '<td class="center">'; - printf( '<span class="issue-status" title="%s">%s</span>', get_enum_element( 'resolution', $p_bug->resolution ), get_enum_element( 'status', $p_bug->status, auth_get_current_user_id(), $p_bug->project_id ) ); + printf( '<span class="issue-status" title="%s">%s</span>', + get_enum_element( 'resolution', $p_bug->resolution, auth_get_current_user_id(), $p_bug->project_id ), + get_enum_element( 'status', $p_bug->status, auth_get_current_user_id(), $p_bug->project_id ) + ); # print username instead of status if(( ON == config_get( 'show_assigned_names' ) ) && ( $p_bug->handler_id > 0 ) && ( access_has_project_level( config_get( 'view_handler_threshold' ), $p_bug->project_id ) ) ) { -- 1.7.5.4 | ||||
related to | 0013682 | closed | dregad | Color codes for custom statuses not displayed cross-project |
related to | 0011323 | closed | dregad | Cross project relationships not picking up custom statuses |
related to | 0013718 | closed | dregad | Custom severity not displayed cross-project |
related to | 0015721 | closed | grangeway | Functionality to consider porting to master-2.0.x |
child of | 0013728 | closed | dregad | Various display issues of custom enums cross-project |
Jan, Please try the attached patch to fix the issue you reported in 0011323:0030651. If that does not resolve your problem, please provide detailed steps to reproduce the behavior you described: "viewing the 'View Issues' page with a project selected that has some subprojects give me a @X@ in some cases where custom resolutions are used" |
|
Hi, unfortunately I am not able any more to reproduce this issue with the resolution field. I could reproduce the very same issue for severity, so I reported a new bug: 0013718 |
|
OK, thanks |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master a20f399b 2011-12-31 12:19 Details Diff |
Fix cross-project display of custom resolution codes When a custom resolution is defined in a different project, its code was displayed as @X@ instead of the corresponding string in the resolution column, as well as when hovering over the status in the view issues page. Fixes 0013707 |
Affected Issues 0013707 |
|
mod - core/columns_api.php | Diff File | ||
MantisBT: master-1.2.x b7644019 2011-12-31 12:19 Details Diff |
Fix cross-project display of custom resolution codes When a custom resolution is defined in a different project, its code was displayed as @X@ instead of the corresponding string in the resolution column, as well as when hovering over the status in the view issues page. Fixes 0013707 |
Affected Issues 0013707 |
|
mod - core/columns_api.php | Diff File |