> Hi Stefan,
>
> Let me tell you my understanding of a
"Release" and a "Group"
Thanks !
> "Release" is especially useful in bug-fixes
and feature implementations.
> We can say that "these" bugs / features would
be fixed / implemented in
> so-and-so "Release" - a kind of a Release
Plan. That is why Eventum is
> also insisting on the date by which the
"Release" has to be out. Beyond
> that date, you will find the Issues pertaining to the
"expired" Release
> magically vanishing but still there in the DB.
Vanishing from where, and when ?
Run a quick test:
Added a release, assigned it to an issue, back-dated the
release but
the issue still shows up in the list for lowly reporters?
Does it only work if the release date "expires
naturally"?
Not that I'm that upset 'bout it - actually this is what I
would prefer
anyway to avoid duplicate entries in the time between the
fix and the
general implementation of the release. Or maybe even later,
if someone
accidently uses an old release ...
> "Group" is nothing but User Group. We can
club bunch of Users into a
> group. I found that this "Group" is not
useful with the default
> implementation of Eventum. .. So you
> need to write a Workflow Class that does this for you.
Ok, that means 'absolutely useless' for me - no clue about
PHP,
therefore no way I gonna write some code ..
Is it only me or _is_ Eventum seriously lacking
documentation ?
Thanks again
yours
Stefan
--
Eventum Users Mailing List
For list archives: http://lists.mys
ql.com/eventum-users
To unsubscribe: http:
//lists.mysql.com/eventum-users?unsub=bond yahoo.com
|