We are working towards making Mantis' defaults work for DCSS. Some of it is tweaking existing fields to suit our needs. But also making a plan what all the possible selections should mean to us, and how they should be used. Please take a look at the tracker, read discussion here and participate!
Starting form the mantis defaults, fields are in progress of being customized to suit the needs of Stone Soup development.
Moved (mostly?) settled-upon help-like content to Mantis Fields Specification.
Categories (BR, FR, support, test) could use subcategories; like the categories in the SF tracker.
In SF, there currently are:
for BRs: None, Arena, Build, Code Conventions, Dungeon, Interface, Items, Lua bindings, Miscellanous, Monsters, Player races, Religions, Spells, Tiles.
for FRs: Atmosphere/Flavour, Documentation, Gameplay Balancing, Interface Improvements, Tiles. — evktalo 2009-11-20 00:03 I would like to have thematical subcategories for FRs for the major topics: spells, gods, species (dpeg).
Could this be handled with tags? — evktalo 2009-11-20 00:03 Yes, but I find the tags to be more clumsy. E.g. for gods, it would best to have them in a separate folder on the moon or so. Subcategories should help in displaying/ignoring them. — dpeg 2009-11-20 00:06
More here: Tags policies
Since we can't add different subcategories to different categories, we'll go with categories and tags. — evktalo 2009-11-26 17:06
Show sticky issues should be on by default.
There needs to be a lot less fields in the filter in general. It looks unwieldy. Especially for FRs; OS/OS version/Platform etc fields are probably good for bug reports? While the simple view is much cleaner for viewing issues, the “simple” filter needs to be simplified.
Yes. Do we really need “Monitored By” and “Hide Status” (whatever that is)? I agree that having both Platform and OS seems redundant, though OS version (specific Windows/Linux version) might come in useful. Agree that Sticky should default to true (and maybe be nonremovable?) I'm not sure what's the difference between “Product Build” and “Product Version”. Is there a way for me to predefine common filters I want to use (such as Tiles specific bugs, or recent feature requests)? — jpeg 2009-11-21 00:59
Yes, you can predefine common filters and make them publicly available, yay! — jpeg 2009-11-21 11:46
Excellent! — evktalo 2009-11-24 09:42
“Recently active Features” should include both Feature Request and Interface Improvement, since the latter is a type of feature request.
Also, some good additional predefined filters would be “My assignments” (assigned to me), “My reports” (issues reported by me), and “My monitored” (issues monitored by me). — Matthew Cline 2009-11-27 12:35
Good ideas! — evktalo 2009-11-27 12:54
Oh, also, the “Open” filters should include both open and re-opened issues. — Matthew Cline 2009-11-27 12:43
With this in mind, what do you think of axing “open”, “re-opened” etc.. resolutions would just be “none, “done”, “rejected”? (the whole proposal is a couple of sections up) — evktalo 2009-11-27 12:54
Also see Customization of "View Issues"
Useful profiles needed: CAO, CDO