View Issue Details

IDProjectCategoryView StatusLast Update
0008983mantisbtcustomizationpublic2019-07-26 18:16
Reportervipart Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status acknowledgedResolutionopen 
Product Version1.1.1 
Target VersionFixed in Version 
Summary0008983: Set default product version
Description

it would be great for users, reporting issues, to set default Product version for example in My Account -> preferences (or somwhere else?). This would let not to enter that value manually every time the issue is being reported.

Also it would be great to do the same thing with "Target version".

TagsNo tags attached.

Relationships

related to 0025946 assigneddregad New Plugins to be transferred 

Activities

vboctor

vboctor

2008-03-27 04:28

manager   ~0017471

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).

vipart

vipart

2008-03-27 06:28

reporter   ~0017473

This way would be great

samtuke

samtuke

2019-05-07 07:08

reporter   ~0062036

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?

spmeesseman

spmeesseman

2019-07-03 21:32

reporter   ~0062351

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

dregad

dregad

2019-07-04 07:09

developer   ~0062353

@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

samtuke

samtuke

2019-07-04 07:38

reporter   ~0062354

@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.

spmeesseman

spmeesseman

2019-07-22 17:47

reporter   ~0062409

Last edited: 2019-07-22 21:01

View 2 revisions

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

Issue History

Date Modified Username Field Change
2008-03-18 05:58 vipart New Issue
2008-03-27 04:28 vboctor Note Added: 0017471
2008-03-27 04:28 vboctor Status new => acknowledged
2008-03-27 06:28 vipart Note Added: 0017473
2019-05-07 07:08 samtuke Note Added: 0062036
2019-07-03 21:32 spmeesseman Note Added: 0062351
2019-07-04 07:09 dregad Note Added: 0062353
2019-07-04 07:38 samtuke Note Added: 0062354
2019-07-22 17:47 spmeesseman Note Added: 0062409
2019-07-22 21:01 spmeesseman Note Edited: 0062409 View Revisions
2019-07-26 18:16 dregad Relationship added related to 0025946