On May 10, 2007, at 15:39 , Oliver Lietz wrote:
Am Donnerstag, 10. Mai 2007 schrieb Grégory Joseph (JIRA):
[ http://jira.magnolia.info/browse/MGNLDMS-97?page=all ]
Grégory Joseph updated MGNLDMS-97:
----------------------------------
Summary: Missing bypasses for dms servlet : opening/
downloading
documents from DMS module results in 404 (was: opening/downloading
documents from DMS module results in 404) Fix Version/s: 1.2
Missing bypasses for dms servlet : opening/downloading documents
from DMS
module results in 404
Hi Greg,
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:
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.
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.
Thanks for the fix anyways ;)
Cheers
g
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
