View Issue Details

IDProjectCategoryView StatusLast Update
0022238mantisbtdocumentationpublic2023-02-22 19:21
Reporterdidaquis Assigned Todregad  
PrioritynormalSeveritytextReproducibilityN/A
Status closedResolutionfixed 
Product Version2.0.0 
Target Version2.25.6Fixed in Version2.25.6 
Summary0022238: Missing columns on $g_view_issues_page_columns documentation
Description

Reading documentation seems not possible show column "eta" on "view_all_bug_page.php" because in explanation of setting "$g_view_issues_page_columns" not especify the possibility of add that column.

Additional Information

Suggestion:

Change this

/**
 * The default columns to be included in the View Issues Page.
 * This can be overriden using Manage -> Manage Configuration -> Manage Columns
 * Also each user can configure their own columns using My Account -> Manage
 * Columns. Some of the columns specified here can be removed automatically if
 * they conflict with other configuration. Or if the current user doesn't have
 * the necessary access level to view them. For example, sponsorship_total will
 * be removed if sponsorships are disabled. To include custom field 'xyz',
 * include the column name as 'custom_xyz'.
 *
 * Standard Column Names (i.e. names to choose from):
 * id, project_id, reporter_id, handler_id, duplicate_id, priority, severity,
 * reproducibility, status, resolution, category_id, date_submitted, last_updated,
 * os, os_build, platform, version, fixed_in_version, target_version, view_state,
 * summary, sponsorship_total, due_date, description, steps_to_reproduce,
 * additional_info, attachment_count, bugnotes_count, selection, edit,
 * overdue
 *
 * @global array $g_view_issues_page_columns
 */

for

/**
 * The default columns to be included in the View Issues Page.
 * This can be overriden using Manage -> Manage Configuration -> Manage Columns
 * Also each user can configure their own columns using My Account -> Manage
 * Columns. Some of the columns specified here can be removed automatically if
 * they conflict with other configuration. Or if the current user doesn't have
 * the necessary access level to view them. For example, sponsorship_total will
 * be removed if sponsorships are disabled. To include custom field 'xyz',
 * include the column name as 'custom_xyz'.
 *
 * Standard Column Names (i.e. names to choose from):
 * id, project_id, reporter_id, handler_id, duplicate_id, priority, severity,
 * reproducibility, status, resolution, category_id, date_submitted, last_updated,
 * os, os_build, platform, version, fixed_in_version, target_version, view_state,
 * summary, sponsorship_total, due_date, description, steps_to_reproduce,
 * additional_info, attachment_count, bugnotes_count, selection, edit,
 * overdue,eta
 *
 * @global array $g_view_issues_page_columns
 */
TagsNo tags attached.

Activities

didaquis

didaquis

2017-01-24 04:56

reporter   ~0055280

Same situation of explanation of setting "$g_bug_report_page_fields". In my opinion, is necessary add "eta" on the explanation of setting.

atrol

atrol

2017-01-24 17:25

developer   ~0055303

There is at least one more bug in this list: There is no field duplicate_id.
There are also bugs in Administrator Guide (display.xml), e.g. category instead of category_id

dregad

dregad

2017-01-25 04:10

developer   ~0055312

I'm wondering if it would not be better to avoid explicitly listing the fields, referencing the actual list in the manage columns page - we are bound to face this type of issues again and again as code evolves, so it becomes a maintenance liability.

atrol

atrol

2017-01-25 04:24

developer   ~0055313

if it would not be better to avoid explicitly listing the fields

+1

didaquis

didaquis

2017-01-25 05:10

reporter   ~0055315

Just asking, I'm not an expert on MantisBT: What is the method for know the names of all posibilities to display if remove that list? It's been listed in other point of documentation or the webadmin needs read the code for found the words?
It's possible to generate the documentation dynamically depending on the options available?

atrol

atrol

2017-01-25 05:24

developer   ~0055316

Last edited: 2017-01-25 05:26

What is the method for know the names of all posibilities to display if remove that list?

Goto page Manage > Mangage Configuration > Manage Columns
or page My Account > Manage Columns

didaquis

didaquis

2017-01-25 05:43

reporter   ~0055318

Great. In that case, the documentation might indicate that the user can see all the options in that section.

OFF TOPIC: Can you explain me how are you making "quotes" in bugnotes?

atrol

atrol

2017-01-25 05:51

developer   ~0055319

OFF TOPIC: Can you explain me how are you making "quotes" in bugnotes?

MantisBT 2.1 will introduce experimental support for Markdown.
It is already enabled on this installation.
This is how it works for end users https://guides.github.com/features/mastering-markdown/

didaquis,
please use the forums for such kind of questions (refer to http://www.mantisbt.org/support.php for links and further details).

dregad

dregad

2023-02-16 10:46

developer   ~0067396

Same situation of explanation of setting "$g_bug_report_page_fields". In my opinion, is necessary add "eta" on the explanation of setting.

This was fixed in 2.24.4, see MantisBT master c6bf4f26

Related Changesets

MantisBT: master b8bf4989

2023-02-16 11:13

dregad


Details Diff
Update $g_view_issues_page_columns documentation

Revise the PHPDoc in config_defaults_inc.php and the Admin Guide.

Also update related $g_print_issues_page_columns, $g_csv_columns and
$g_excel_columns.

Fixes 0022238
Affected Issues
0022238
mod - config_defaults_inc.php Diff File
mod - docbook/Admin_Guide/en-US/config/display.xml Diff File