Re: [Mantisbt-dev] Re: [mantisbt 0003008]: this mantis installation: want to be able to close my own bugs, not only to reopen them

[Olyves <hu...@ol...>]

> Why another status?
>
> Can't you use "resolved" to mark it as such in house and then have the
> customer "close" it (which would equal delivered and approved)?
We make a difference between "solved on the developper's desk" and "solved
on the client's desk" because of the delay between the bug fix and the
release installation on site
The bug is closed only after a successfull test campain in the production
environment
>
> We close bugs here when we deliver. If the customer still has an issue
> with the problem, he opens a new bug...
This works great too...
>
> If you make the customer close it, you will have a lot of follow-up work
> to do. The other way around, the customers will be more pro-active. I
> also think that the customer-closes-bugs concept doesn't work for people
> who use it publicly to track bugs in their projects on the internet.
> People who submit bugs will almost never follow up once they get what
> they wanted.
On the other hand it's interesting to initiate a contact with the customer
for a positive raison (a problem is solved) as bugs are not very frequent -
we use mantis during the development and beta stade on a private basis only
>
> Cheers,
>    Andre
>
> Olyves wrote:
>
> >>While I agree that having users confirm that the fix works for them is
> >>a good idea, the problem is that they often don't.
> >>
> >>
> >Here, we never close a bug ourselves and allways ask the client to do so
> >(and it can be time consuming)
> >
> >
> >
> >>Does anyone have any comments on our policy of leaving bugs open until
> >>we release the fixes?  Do we need to add another status after CLOSED and
> >>allow reporters to close their bugs?
> >>
> >>
> >I think we need another status after CLOSED (something like DELIVERED AND
> >APPROVED)
> >Actually, people are asking me every day when this feature will be
> >implemented
> >
> >Yves
> >