I am currently trying to understand how it is possible to customize MantisBT without changing core code (which I did before ... but now I wanted to do it the right way after I updated MantisBT on my local server).
Is it somehow possible to let MantisBT redirect to the "view_all_bug_page.php" after I created an issue / a bug?
Till now I changed the redirect code in the bug_update.php, IIRC. But this is - obviously - a core file.
Thanks for your help!
Last edited by Tagirijus on 30 Sep 2020, 12:46, edited 1 time in total.
Currently there is no alternative for what you ask
Hm, what a bummer. ... I am still trying to dig the plugin event hooks etc. Are you familiar with these and would say even with such event hooks it would not be possible?
With the standard available events it is not possible. Of course you can define your own events but then you need to adjust core files to add that event.
So think you are stuck with adjusting core files. Biggest challenge there is to maintain a complete overview of all changes made in case of future updates.
Possibly for other customizations plugins do exist, so do not give up
Weeeeeeell, haha. I made it! I actually started to write a plugin, which allows me (or others, since I made it public!) to enable some workflow tweaks. The "redirect to table after report or update" is one of these points. Feel free to use it:
Just wondering about the action to give new status to issue when assigned since this is standard available
Do you mean the option on the work threshold page? Somehow this option has no effect here ... or I simply don't understand it. But in the end my plugin works like I want it to, for now, hehe.
I just took some time to watch through the whole file: thanks for the hint, since I found some development and logging / error display options, which might become handy in the future, when developing, hehe.
Besides this, I did not find anything useful for my workflow wishes, unfortunately. The $g_bug_assigned_status did not work as I thought it would (actually it didn't make a difference). Either its buggy, or it's just something completely different than I expected, hehe. Again: I stick to my workflow plugin. It's almost done anyway. (=