Mantis Bug Tracker - Forums

I would start without any java, just include a simple php script that retrieves the data and displays it. Like always Keep it Simple.

Hi Sara,
you say you need to have custom field with ID = 59 but you are retrieving field with ID = 55.
In addition you are only saying it is not working but what is not working? Are there any java errors reported or is the new field not showing everything?

Did you try the email check in the admin section?

There is the forward plugin which you could modify to become active on the EVENT_REPORT_BUG. Next add the attachment to the mail. Perhaps that will work for you.

The attachment filenames are stored in the the file_table including the type of file. So there you can find them. Out of the box theer is not much possible with the emails as such. I did create an option to define your own templates for emails but that does require some adjustments is core files. Th...

This is not available out of the box.
You can develop this feature and contribute. If that is not an option, you can report it @ www.mantisbt.org/bugs

You can check on a strange entry for this user in the tokens_table. You can simply remove those entries (using phpmyadmin or something similar) and have the user try again.

VL284, there is an easy way to reference to an issue/note within Mantis. Have a look @ https://mantisbt.org/forums/viewtopic.php?t=19315
The quoting button is something we can look at if this is also not enough

In case you make changes to the default (workflow) settings, they will be stored/updated in the config table so that is where you need to be.
As for columns, each user can do that under their My Account section. For more generic access, one needs to have access to the Manage pages.

@vl284, how about creating a plugin that achieves that behavior?

I am not ware of such a plugin being available.
The easy way is to coy/paste whatever you like to quote

In general a lot of that is derived from the roles. Default settings you can find in config_defaults_inc.php

Well you can look at assigning corresponding levels, that will be able to solve must of the possible changes, just user Reporter/Developer & Manager.
This however will limit the strength of the tool.
Any changes are looged so one knbows what has been changed when and by whom.

What you then can try is to extend the existing plugin with checking a table which holds the "weak" passwords.

So nobody can edit anymore? Strange cuase then it stays assigned. I take it you mean that only the assignee can edit the post?
If that is what youe mean, as far as I know that would require changes to core files.