Mantis Logo
Mantis Manual
Manual
Page Descriptions

Login page
Main page
View Bugs page
Bug View Simple page
Bug View Advanced page
Bug Change Status page
Bug Update Simple page
Bug Update Advanced page
My Account Page
System Management Pages
Monitor Bug
Reopen Bug
Delete Bug
Close Bug
Assign to Me
Resolve Bug
News Syndication


Partner Links


View Bugs page
Last Modified: April 24, 2006 16:04PM
(Any)
Description

Here we can view the bug listings. The page has a set of viewing filters at the top and the bugs are listed below.

Filters

The filters control the behavior of the bug list. The filters are saved between browsing sessions but do not currently save sort order or direction.

If the number of bugs exceeds the "Show" count in the filter a set of navigation to go to "First", "Last", "Previous", "Next" and specific page numbers are added.

The Search field will look for simple keyword matches in the summary, description, steps to reproduce, additional information, bug id, or bug text id fields. It does not search through bugnotes.


Bug List

The bugs are listed in a table and the attributes are listed in the following order: priority, id, number of bugnotes, category, severity, status, last updated, and summary. Each (except for number of bugnotes) can be clicked on to sort by that column. Clicking again will reverse the direction of the sort. The default is to sort by last modification time, where the last modified bug appears at the top.

The bug id is a link that leads to a more detailed report about the bug. Depending on what you have set in your Account Preferences you will be sent to the simple or advanced view. You can also add bugnotes here.

The number in the bugnote count column will be bold if a bugnote has been added in the specified time frame. The addition of a bugnote will make the bugnote link of the bug appear in the unvisited state.

The text in the "Severity" column will be bold if the severity is major, crash, or block and the bug not resolved.

The text in the "Updated" column will be bold if the bug has changed in the last "Changed(hrs)" field which is specified in the viewing filters.

Each table row is color coded according to the bug status. The colors can be customised through Mantis Configuration.

Severities

block - prevents further work/progress from being made
crash - crashes the application or OS
major - major bug
minor - minor bug
tweak - needs tweaking
text - error in the text
trivial - being nitpicky
feature - requesting new feature

Status

new - new bugs
feedback - bug requires more information, the original posters should pay attention
acknowledged - bug has been looked at but not confirmed or assigned
confirmed - confirmed and reproducible (typically set by an Updater or other Developer)
assigned - assigned to a Developer
resolved - bug should be fixed, waiting on confirmation of fix
closed - bug is closed

Moving the mouse over the status text will show the resolution as a title. This is rendered by some browsers as a bubble and in others as a status line text.

User Contributed Notes
View Bugs page
Add Notes About Notes
mracicot@matrixplus.com
16-Mar-2004 13:54
#87
Is it possible to add a couple of columns in the view all bugs page? I would like to see the "Resolution" field and maybe the option to add a custom field like "Release note (Y/N)". I am not a PHP programmer nor do I play one on TV so I could use a little feedback from the Mantis community.
dan@danjkelly.com
25-May-2004 17:23
#142
I too would like to be able to customize the View bugs page. Or, as an alternative, I would like to be able to cucstomize the fields that appear on a CSV export. I need to add Description and would suppress a few others.
robert.wainberg at Fisher-price dot com
28-Jun-2004 11:00
#162
I think "feature" is out of place within the severity category.

We use this tool to track both bugs and requests for new features/enhancements.

It would be helpful to be able to filter by either bugs or enhancements.

I'm sure we can set up the tool to do this, but I believe it would help all users for this to be a default setting.

Regards.
gksus@nm.ru
12-Jul-2004 4:50
#168
It's a good idea to fill page title with <Bug #nnn>.
When I open some pages in my browser at the same time, I see: Mantis,Mantis,Mantis - on the top of tabs.

With regards, Nikitin Misha.
contact =at= creative-perspectives.com
21-Oct-2004 19:32
#240
There's one critically important status item that's missing, which is "deferred". Right now, we're tracking deferred items with a tag in the bug summary field, but it would be really nice to be able to defer a bug (and hide it in the view lists) simply by changing its status.
no@email.com
28-Nov-2004 22:23
#272
Thinking about relationships between bugs, it would be really handy if these were shown somehow on the view bugs page. Maybe an option to nest related bugs, eg
bug #001
bug #002
   bug #003 (child of #002)
   bug #004 (child of #002)
      bug #005 (child of #004)

...etc...

Regards,

M@
bfedus@speakeasy.net
31-Dec-2004 2:31
#303
Hello, is there any way to make the filter view in ver 0.19.2 look and work like it did in ver 0.18.3, In that version it was nice because you had a sigle line of filters and you could use the drop-down menu right on the bugs page, rather than having to go to a seperate page to filter.

I manage a team of engineers and we use Mantis for issue tracking and it would be easier to use the filter to keep track of who is working on what.

Thanks
cp@sandon.it
09-Feb-2005 9:12
#346
I would add a "type" field, which should hold the issue type, for example "bug", "non conformance", "enhancement", "new feature", "documentation", or something alike. It would tell what kinf of issue it is, regardless of its severity.
crocuss16-bt@yahoo-n-o-s-p-a-m.com
04-Mar-2005 6:13
#369
@bfedus: I also posted a question for that under 'configuration:filters'.

The only way I made this work for now was to edit the function calls themselves. I don't know if this will be appreciated much, but I'll include some instructions here.

file: core/filter_api.php
function: filter_draw_selection_area

collapse_open( 'filter' );
filter_draw_selection_area2( $p_page_number, $p_for_screen, true );
collapse_closed( 'filter' );
filter_draw_selection_area2( $p_page_number, $p_for_screen, false );

-> swap the 'true' and 'false' in the calls and the filter section will be collapsed by default.

I hope that later there will be support for this in the config_inc file.
kmliu@sunplus.com.tw
28-Mar-2005 7:17
#390
Why the bug id start from 0000002 instead of 0000001 ?
jeetendrae@cybage.com
03-Jan-2006 0:51
#799
In the View Bugs Page we could find explanation about Severities. But we would also require explanation about Priorities of the bugs.
j.heinz@sz-sb.de
06-Jan-2006 7:26
#806
#I'm currently using a customized version 0.18.0rc1 of Mantis.
#Allthough I don't know if it is meanwhile possible to use filter search
#over custom fields too in newer versions, here is my solution to make
#it possible:
#You need 3 changes in core/filter_api.php in
function filter_get_bug_rows(.....

#on top of this function add:
$t_custom_field_project_table=config_get('mantis_custom_field_project_table');
$t_custom_field_string_table=config_get('mantis_custom_field_string_table');

#then change
#array_push( $t_where_clauses,
#"((summary LIKE '%$c_search%')
# OR ($t_bug_text_table.description LIKE '%$c_search%')
# OR ($t_bug_text_table.steps_to_reproduce LIKE '%$c_search%')
# OR ($t_bug_text_table.additional_information LIKE '%$c_search%')
# OR ($t_bug_table.id LIKE '%$c_search%')
# OR ($t_bugnote_text_table.note LIKE '%$c_search%'))" ) ;
#
#by:
array_push( $t_where_clauses,
"((summary LIKE '%$c_search%')
 OR ($t_bug_text_table.description LIKE '%$c_search%')
 OR ($t_bug_text_table.steps_to_reproduce LIKE '%$c_search%')
 OR ($t_bug_text_table.additional_information LIKE '%$c_search%')
 OR ($t_bug_table.id LIKE '%$c_search%')
 OR ($t_bugnote_text_table.note LIKE '%$c_search%')
 OR ($t_custom_field_string_table.value LIKE '%$c_search%')
    ; )" ) ;
# as you see the -OR- part with $t_custom_field_string_table is new
#
# then add a new JOIN clause:
array_push( $t_join_clauses,"LEFT JOIN $t_custom_field_string_table ON $t_custom_field_string_table.bug_id = $t_bug_table.id"; ) ;
# that's all
# injoy,
# regards, Johannes Heinz
datamodel@gmail.com
09-Mar-2006 8:53
#921
09-Mar-2006 8:52
How do I add extra columns in the Bugs view page? I'd really like to do that and maybe remove some columns too. Specifically I'd like to add columns for some custom fields. Can someone share the steps to do that please? thanks.

Data.
cyrisse@cyrisse.com
13-Mar-2006 8:01
#932
If you want to add or remove columns from the View All Bugs page, or want to change the order of the columns, follow the instructions below:

Open this file: /core/custom_function_api.php
Look for this function: custom_function_default_get_columns_to_view

Here you can set the columns that will appear on the page, and in the CSV export. The first part of the if-block will set the columns for the CSV, after the else you can set those for the page itself.

If you want to change order of some column, cut that line, and paste it above/below the column you want it to appear.

You can also remove or add columns by adding new lines, just make sure they are similar to the other lines ($t_columns[] = 'summary'; for example). You will find what fieldnames to use when you examine the existing lines.
alberto.requena@gmail.com
16-Mar-2006 4:34
#941
Hi,
I'm wondering how can I delete several priorities, for instance crash priority which i don't need it at all.
I suppose I have to change a php file but I don't know neither which file is nor what I should change.

Thanks for your helpĀ”
dirk.tempelhagen at sabre.com
20-Mar-2006 6:31
#950
Hi!

I would like to know if it's possible to add some custom fields in the mentioned "core/custom_function_api.php"?
I tried it without success. But I think there is a way to do it.

Thanks,
Dirk
stevenbenbow at quintessa.org
22-Mar-2006 6:59
#958
To add custom fields to the view, open custom_function_api.php (as described above), and add

   $t_columns[] = 'custom_CUSTOM FIELD NAME';

where CUSTOM FIELD NAME is the verbatim name of one of your custom field (i.e. including appropriate whitespace).
D onald G ri eve at r t e l dot c o m
24-Mar-2006 5:48
#965
Created 2 projects and raised some bugs on one. Then on the second project on submitting a bug it increments from the last bug raised on the other project. So my new bug on new project starts at ID 000014 instead of 0000001. Is it possible to reset bug ID value to 1 per project?
rbartz@descartes.com
21-Apr-2006 13:41
#1017
We just installed the latest Mantis version but are experiencing the same filter issue that was reported fixed. Maybe its a process issue, if I select to see all Resolved Issues and hit Search, the Status field defaults back to Closed and I get all issues. Is this the right process? Did we miss a patch?
ionut_juncu@yahoo.com
23-May-2006 5:49
#1088
in query browser apply to bugraker database

TRUNCATE TABLE `mantis_bug_table`

to start from 000001

:)
jessicalilyang@hotmail.com
14-Jun-2006 2:18
#1135
Now I am using Mantis 0.19.3 .I also want to add Description colomn in the CSV export ,and I tried the \core\custom_function_api.php,but can not find the function that mentioned above.

abramdevonshireathotmaildotcom@hotmail.com
17-Aug-2006 14:47
#1237
I can add a column, but how do you set the column to only show for the currently selected project?
emailisrequired@email.com
29-Aug-2006 6:09
#1252
Is there any way to expand the reporting options? As a professional software tester, it is not only my responsibility to find and log issues, it is also my responsibility to report to the management. The existing export-features are rather limited and have a very unclear structure).
Also a real overview about the number of issues closed and so on would be very interesting.
no email @ please
05-Nov-2006 13:11
#1287
Can I sort by two custom fields?

When I do so it looks like your query doesn't alias the custom field table so there's ambiguous (duplicate) reference in your sortby clause.

You should definately be aliasing tablenames anway to support exactly this kind of extension.
twilson3764@NOSPAMgmail.com
30-Dec-2006 1:59
#1325
I made a simple change so I could link directly to a bugnote attached to an issue. Open up bugnote_view_inc.php and add the second line of code after you see the first line listed here:

<tr class="bugnote" name="<?php echo $v3_id ?>" id="<?php echo $v3_id ?>">
    <a name="<?php echo $v3_id ?>">

Now you can link to any bugnote with view.php?id=issuenumber#bugnotenumber. I also changed the displayed bugnote number to be a link to that bugnote for easy linking. Two lines down from the line you just added change it to this:

<span class="small">(<a href="<?php echo $myurl."#".$v3_id?>"><?php echo $t_bugnote_id_formatted ?></a> )</span><br />

The variable $myurl can be built like this:

$myurl = "http://".$_SERVER['HTTP_HOST'].$_SERVER['PHP_SELF']."?".$_SERVER['QUERY_STRING'];
Add Notes About Notes
Last updated: Mon, 06 Oct 2008 - 13:58:01

Mantis @ SourceForge