On Thu, Jan 02, 2014 at 11:08:40PM +0000, Steve Fryatt wrote:
On 17 Dec, Vincent Sanders wrote in message
> Finally the resolved status implies that the resolution field should be
> looked at to see how the issue was resolved and the closed status implies
> the developer has finished with the report and no additional activity will
> be made on the issue.
When closing tickets and filling in "Fixed in CI build #", should I also be
setting "Fixed in version" to something sensible, or is that caught
automatically when a stable release happens?
The "Fixed in version" should be set to the next release version
(currently 3.1) I set the field on the one you recently closed for
you. This is purely so the mantis "change log" and "roadmap" sections
get updated which is useful when the release notes are written letting
us see which bugs we fixed in a release.
Also, should I actually be closing tickets when resolved, or just setting
them as "resolved"?
We are using resolved to mean the separate resolution field has been set
correctly and the issue was real and is now delt with whereas closed
is for situations where the issue was not actually resolved
(duplicates, not actually a bug etc.) very much a developer choice
there so up to you.
I will mention again that we are not using the priority field at all
so please do not alter it from its default (if I could figure out how
to turn it off across the whole UI I would.)
Steve Fryatt - Leeds, England