Since a Mantis installation can include multiple projects and the user may be using a different version per project, it doesn't make sense to have this in the preferences. However, what we can do is to remember the last reported version per project and use it as the default for future bug reports. This can be potentially implemented by storing a user token which includes the last used version for each project that the user has reported issues against. We also have to handle the last used version no longer exists in the project versions (just in case it was deleted by the project manager, although unlikely).

This way would be great

We are also seeking this feature. Any way to set the default product version project-wide, ideally to always be the most recently released version?

Late replies, but just leaving this here for reference, I just happened upon this ticket... I wrote a simple plugin to do what @samtuke mentions here... https://github.com/spmeesseman/mantisbt-plugins/tree/master/DefaultVersions (is it ok to post external links?). sll my plugins are relatively brand new and only lightly tested so far in production so you might need to tweak the code, or just make an issue post on my github

@spmeesseman I would suggest, instead of bundling all your plugins into a single repository, to split that into multiple repsitories (one per plugin).

And then, to give them more visibility, move the repos to the mantisbt-plugins organization and reference them in the wiki

Details: https://mantisbt.org/wiki/doku.php/mantisbt:plugins:start#the_github_mantisbt-plugins_organization

@spmeesseman Thanks for the plugins, and pointing them out!

I agree with @dregad that his suggestions would make the plugins easier to find and use.

sorry, i had to make my stuff private for now because of a situation. I will make it public again soon.