New feature: change native fields to predefined custom ones

[rbeton]

I really like Mantis' custom fields. However a colleague said she was impressed with Mantis but what could it do for hardware projects? Could it track general customer trouble tickets?

Out of the box, the answer is "no" it seems. But it would be easy to make Mantis more easily customised: simply reduce the number of native fields and replace them with predefined custom fields. Then the existing custom fields user interface would allow administrators to remove fields that only apply to software projects, replacing them with fields suitable for other types of projects.

Let's consider the native fields:

*Category: this applies to every project. No change.

*Reproducibility: this applies to all "trouble-ticket" type of projects but may not be required if Mantis is just used for a shared 'to-do' list, for example.

*Severity: the options are ideal for most software issues, but other kinds of projects might need slightly different options.

*Priority: any to-do list needs this. No change.

*Platform: often not applicable to non-software projects.

*OS: usually not applicable to non-software projects.

*OS version: usually not applicable to non-software projects.

*Product build: this one applies reasonably generally to work that has reached product status - but there are many conceivable uses for Mantis where it's irrelevant.

So the minimal set would need only Category and Priority. Keeping Reproducibility and Severity might be sensible to make the impact of the change on Mantis less disruptive. All the others could easily be made available through custom fields pre-entered during the installation phase.

Overall I think Mantis is great and could be even better.

Rick

[rags]

I am trying to remove native fields "Priority", "Projection" from a new project whih i created recently. Please let me know how to do? Also can you please explain me how to set a view Filter for a user for a project which should also export csv with few more custom fields.

Pelase help me in doing this as I stuck with these two items. I am using Mantis version 1.0.3 .

Thanks in advance.

[vboctor]

In MantisBT 1.2.0rc2 (yet to be released), it is now possible to hide/show most of the fields. You can now easily reduce the fields in the report / view / update / print pages to:

1. Category
2. Summary
3. Description

Everything else is optional and can be easily hidden. Even the category fields can potentially be removed as well. This should make it easier to customize MantisBT for use with non-software projections.

Also the values available for enumeration fields can be customized as necessary. This is already available for version 1.1.x and from before.

[gdelvec]

What are teh steps required to hide a field in the report form in Mantis 1.2.0rc2? Thanks

[worschtsupp]

Done a quick try:

• Have a look at config_defaults_inc.php, search for $g_bug_report_page_fields.
• Copy the array to your config_inc.php.
• Delete / comment out the lines (=fields) you don't need.
• Be aware: you can not remove every field you like, some must stay (see comment)

Don't know if this is sufficent or if you ahve to eleminate the fields from report / lists, too. This can be done in Mantis itself as well.

[elt0n]

Done a quick try:

• Have a look at config_defaults_inc.php, search for $g_bug_report_page_fields.
• Copy the array to your config_inc.php.
• Delete / comment out the lines (=fields) you don't need.
• Be aware: you can not remove every field you like, some must stay (see comment)

Don't know if this is sufficent or if you ahve to eleminate the fields from report / lists, too. This can be done in Mantis itself as well.

So I want to show these fields on edit update and view pages:
projection, due_date, overdue

but it doesn't work the way you described it. I'm working with Mantis 1.2.0rc2.

[worschtsupp]

but it doesn't work the way you described it.

So what, elt0n, and what do you expect now? Guessing the community what maybe wrong? Praying to give us details?
First of all: this topic was about how to remove(!) fields from something, not the other way round. If you are sure that it should work, than feel free to file a bug at the mantis-bugtracker, so the developers there will have a chance to fix it. And mention the bug-id here.

Or try a fresh nighly build before filing a new bug.

Let us no how you solved it.

[Realtime]

Hi!

• Have a look at config_defaults_inc.php, search for $g_bug_report_page_fields.
• Copy the array to your config_inc.php.
• Delete / comment out the lines (=fields) you don't need.
• Be aware: you can not remove every field you like, some must stay (see comment)

Don't know if this is sufficent or if you ahve to eleminate the fields from report / lists, too. This can be done in Mantis itself as well.

I try this and it work fine with my mantis 1.2.0RC2.

... BUT ...

I want to enable / disable the columns for each project (e.g. the embedded projects don't need a PC-configuration but a version oft the hardware).

I go to manage_config_columns_page.php an try to disable (for the test) all of the colums except id column, like the test above.

I control the settings with adm_config_report.php. There I can read:
All Users / All Projects / view_issues_page_columns / complex / array (0 => 'id',)

I expect that only the id was shown in view.php, but all of the columns where shown.

Is this a bug in RC2 or does I made a mistake?

TIA, and sorry for my bad english.


Marc

[Realtime]

*push*

Hi!

Does nobody uses this function to enable / disable the coulms via manage_config_columns_page.php and not "hardcoded" in config_defaults_inc.php?

Should I open a bugreport?

TIA!

Marc

[FreeEMS]

This worked for me, as follows:

Configuration Option:

Code: Select all

bug_report_page_fields

Set the project, set the users to all from your self, and Value:

Code: Select all

array(
                'category_id',
                'view_state',
                'handler',
                'priority',
                'severity',
                'reproducibility',
                'product_version',
                'product_build',
                'target_version',
                'summary',
                'description',
                'additional_info',
                'steps_to_reproduce',
                'attachments',
                'due_date',
        )

And it parses it and uses it just fine.

You have to remove the g_ from the front of the config var name, and the semicolon from the value, but otherwise its a copy paste edit configure job.

MantisBT version 1.2.5 for the record

Fred.