Am Donnerstag, 10. Mai 2007 schrieb Grégory Joseph: [...] > > is adding the cause to the summary the preferred style when opening > > (when > > already known)/closing an issue? > > I have no fixed rules, but try to keep in mind the "changelog" usage:
Ah ok, that makes sense. > the fact that you got a 404 in dms could be for a gazillion different > reasons. A user seeing this fixed could think "oh, so there were > severe bugs in dms", or "oh, so that's what I have, it's fixed, let's > update" while their 404 was for a totally different reason. normally one would check details of the issue... but oh users... :) > While we're on the subject - at least until we keep the current/ > default setup for jira workflows, I'd like to mention I usually > prefer issues to be "resolved" rather than closed, at least until a > release is made: 1) we can still edit them 2) to me, the "closed" > status means: this has been verified and validated by the "user", so > it shouldn't be done by a developer - again, no rules fixed in stone, > just my thoughts which are changeable and discussable. hehehe - I read http://www.atlassian.com/software/jira/docs/latest/default_workflow.html and http://www.atlassian.com/software/jira/docs/latest/issues.html#StatusTypes and checked the frequency of occurrence of "Closed" and "Resolved" just before working on that issue in Jira today. I was also the user who reported the issue and tried my patches before committing them of course. So I came to the conclusion that using "Close" fits best. I'm happy with using resolve or close as long we use it in a consistent way. When working on the bypasses issue I browsed through the new voting package and found some small things - e.g. missing license header, unnecessary semicolon. We don't create issues in Jira for that trivial things, do we? Is there a rule of thumb which issues should be documented in Jira? I suggest using the SVN revision in Jira when resolving issues so we have a reference from SVN to Jira and also the other way round. That's the way I do it here with Trac and SVN. There is not a feature in Jira to link from an issue to the related source in SVN like there is in Trac, is it? > Thanks for the fix anyways ;) in the spirit of open source - use it, improve it Thanks for providing Magnolia and opening it more and more. O. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
