On 2010/08/26 08:34, Michael Haupt wrote:
> Hi,
>
> On Thu, Aug 26, 2010 at 4:55 AM, Ken Causey<ken at kencausey.com>  wrote:
>> OK, I went ahead and assigned 'casey' as the default for the
>> Documentation project, it can always be changed again if necessary.
>
> can assignments be changed? I.e., if all doc issues are automatically
> assigned to Casey, could I, if I have some time on my hands, grab one
> of the issues from him, assign it to me, and thereby point out that
> I'm working on it?

Yes: either the currently responsible person may assign the task to you, 
or you may (given suitable permissions) take over a task by assigning it 
to yourself.

> (Is there a difference between "assigned" and "being worked on"? I
> wouldn't want to grab assigned issues from Casey on which *he* is
> already working.)

I'm not sure of the precise meanings the community associates with the 
different task states. I interpret "assigned" as "this person's either 
investigating the task, or working on it in some other way, but at any 
rate is currently responsible for the task".

If you're working on a piece of documentation - say, WebClient - you 
could always bounce the task to the maintainer of that package (Andreas, 
in this case) by moving the task state to feedback. (This prompts you 
for a name, and possibly a note.) Mantis then sends that person an 
email, so one doesn't have to poll Mantis all the time.

I'd expect, for a bug report, for a task to go new -> assigned -> 
confirmed, and then maybe request feedback from someone (-> feedback) or 
"it's not a bug" (-> closed) or "yes it's done and here's the fix (-> 
resolved -> closed).

For documentation, I think simply assign -> resolved (or maybe -> 
feedback -> resolved) -> closed should be fine?

frank