Mantis Bug Tracker - Forums

If it is only to file issues, suggest you use the email-plugin. This way customers can raise an issue by simply sending an email.
The plugin has various options for anonymous reporting but also for automation of account creation

Check in the history for the field Resolution getting the value "Reopened" or whatever value you have assigned to $g_bug_reopen_resolution

Hi Elyes,
thanks for spotting this.
Problem here is that the event "EVENT_UPDATE_BUG", is not integrated in the used functions from the view issues page.
So rather than adjusting core, think this should be fixed by the mantis team.

well then add a custom field to handle this (standard functionality), pretty straight forward.

For understanding db_param you better check out the database _api, here is as sample from bug_api how it actually works: $query = "SELECT COUNT(*) FROM $t_bugnote_table WHERE bug_id =" . db_param() . " $t_restriction"; $result = db_query_bound( $query, Array( $this->bug_id ) ); S...

Did you try restarting your webserver?
If so, did you clean the caches and temp folders too?

Simply use the Custom Reporter plugin. Then you can select the reporter while creating the issue.

Those fields are handled by the system, you cannot change those. Well you could do that in the database but will prove to be pretty cumbersome (rightly so!).

So you only want the ticket to be visible as of the next day?
That is not possible @ this moment , would require major review of this plugin.

Currently that is not an option. The next ticket is triggered by a certain status. :mrgreen: Now if you would use the staus onfirmed, you could use that status to trigger the next ticket, still based upon status. :roll: So when you create a daily recurring task, would you then expect the system to g...

New version is available, check it out here:
http://www.mantisbt.org/bugs/view.php?id=7260

Will see if I can handle this in the coming weeks.

@Elyes, please follow instructions with respect to the config_inc and custom_strings_inc scripts. That will take care of the issue.

@noc, same advice. It will create a new issue/task once the active issue reaches a certain status. This again is configurable via plugin management

Have to disappoint you, that is not an option at this moment in time.
Would be relative easy to add a switch to convert only active issues.
However the old user would need to stay in the system

You can find things here:
http://www.mantisbt.org/bugs/view.php?id=7260