Mantis Bug Tracker - Forums

The "helper_project_specific_where" function in core/helper_api.php is used to find the subprojects of a project. When reporting a new bug, this function is called several layers deep. Modifications to this function will likely impact other operations that might also call it. I've tested a one line ...

When I first read the original question, I thought the requested purpose was if the actual reporter (person who placed the call) did not have a mantis account, i.e. an external client. In that case, you can create a custom field for the external client's information.

Before installing mantis, we ...

This can be accomplished in typical Mantis style by adding a redirect link after the "Operation Successful" notice is printed and allowing the user to select the project before the redirect takes them back to the Manage Projects page (like it does when you create an issue). Or, it can be made to ...

See http://www.mantisbt.org/forums/viewtopic.php?f=4&t=7747

While not exactly what you want, we have customized the Roadmap to include a "Target Date" for release. So we still have the progress bar based on % of issues completed, but also have a target release date for each issue and the farthest date in the future of all issues associated with a version is ...

We've used the custom field feature to create a target date (a softer way to say deadline). The code was then modified to display the target date in the Roadmap (as well as showing up in individual issues as part of the built in custom field functionality).

The following post has more information ...

Based on the way tages are implemented, it looks like this would be quite difficult because the tag operations use separate functions and are not just a field in the create issue page. One problem I foresee is that when you try to attach the tag, the record that you are trying to attach the tag to ...

1 You can modify the columns shown in the view_all_bugs page using the configuration files. Copy this line from config_defaults_inc.php:

$g_view_issues_page_columns = array ( 'selection', 'edit', 'priority', 'id', 'sponsorship_total', 'bugnotes_count', 'attachment', 'category', 'status', 'last ...

We wanted to see more information on the Roadmap, including target release dates. In order to do this, we created a custom field for the date "target_date." In order for this to show as "Target Date" on the issue update page, we included the following code in mantis/custom_strings_inc.php (see http ...

Update: I'm sort of new to Mantis and just learned the preferred way to update custom strings is typically through custom_strings_inc.php, which should be placed in the mantis root. For language support of customs strings, you need to include code to select the proper language - see http://www ...

Two possible solutions include:

1. modifying the code in bug_update_advanced_page.php

<select <?php echo helper_get_tab_index() ?> name="eta">
<?php print_enum_string_option_list( 'eta', $t_bug->eta ) ?>
</select>


Replace the <select> statements with code for an input box. You will need to ...

A minor code modification can add "Release Pending" (or something similar) to the titles of unreleased versions that show up in the change log. See the following post in the Customization section of this forum.

http://www.mantisbt.org/forums/viewtopic.php?f=4&t=7729

The strings are stored in the lang/ folder. Search strings_english.txt (or language file of choice) for "Summary" (or word of choice). There are several places you will want to change this in addition to the root definition $s_summary = ' Summary '; . For example, you will probably want to change it ...

Following up to the post in the General Discussion about seeing versions/issues in both the change log and road map (http://www.mantisbt.org/forums/viewtopic.php?f=2&t=6968), below is an easy solution that adds "Release Pending" to versions in the change log that are not yet released. These ...