View Issue Details

IDProjectCategoryView StatusLast Update
0014841mantisbtcustomizationpublic2019-05-22 15:39
Reportermctuft Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
Product Version1.2.11 
Summary0014841: Unable to customise fields shown on "change status" pages
Description

There is no way to customise which fields appear on the "Change Status" pages.

Customising $g_bug_change_status_page_fields in config_inc.php has no effect.

It would be nice to have customisable field lists for each status level:

$g_bug_change_status_unresolved_page_fields
$g_bug_change_status_resolved_page_fields
$g_bug_change_status_closed_page_fields

Steps To Reproduce

Customise $g_bug_change_status_page_fields in config_inc.php, removing 'view_state' from the list.

View a bug and hit the "Change status to" button.

The "View status" field still appears on the "change status" page.

TagsNo tags attached.

Relationships

related to 0015266 closeddregad Include an option for an "Assign to" page (similar to "Resolve" and "Close") 

Activities

dregad

dregad

2012-12-07 09:20

developer   ~0034505

Instead of defining several global vairables, it would probably be a better design to have this as an array specifying fields that should be displayed for each status (it would also provide additional flexibility).

kelson

kelson

2014-04-14 11:45

reporter   ~0040098

Hi,

In MantisBT 1.2.17, in bug_change_status_page.php, I found at line 44 :
$tpl_fields_config_option = 'bug_change_status_page_fields';
However, $tpl_fields_config_option is not used anywhere.

What about of this configuration option ?

Cheers

TomR

TomR

2014-11-27 12:43

reporter   ~0041931

Is this still an issue.

It seems so, because we want to remove 'resolution' field evertwhere.

However it stills shows up on bug_change_status_page.php

Anyone with q quick fix?

alexandre.boc-ho

alexandre.boc-ho

2015-02-19 05:47

reporter   ~0048874

Hi,
News about this bug?

Cheers

windrienk

windrienk

2017-08-03 05:38

reporter   ~0057380

I had the same problem, I fixed it by removing/commenting the code in bug_change_status_page.php. Each field has his own piece of html and php code in there so you can comment/remove it.

tvdmaas

tvdmaas

2017-09-21 06:06

reporter   ~0057774

It would make the handling process more intuitive if this would work because not all fields are always mandatory ....

Issue History

Date Modified Username Field Change
2012-10-18 05:41 mctuft New Issue
2012-12-07 09:18 dregad Relationship added related to 0015266
2012-12-07 09:20 dregad Note Added: 0034505
2012-12-07 09:20 dregad Status new => acknowledged
2014-04-14 11:45 kelson Note Added: 0040098
2014-11-27 12:43 TomR Note Added: 0041931
2015-02-19 05:47 alexandre.boc-ho Note Added: 0048874
2015-03-02 08:04 vitsaadmin Issue cloned: 0019428
2017-08-03 05:38 windrienk Note Added: 0057380
2017-09-21 06:06 tvdmaas Note Added: 0057774