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 close bugs here when we deliver. If the customer still has an issue
with the problem, he opens a new bug...
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
>>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
>Actually, people are asking me every day when this feature will be
>This SF.net email is sponsored by: Scholarships for Techies!
>Can't afford IT training? All 2003 ictp students receive scholarships.
>Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
>Mantisbt-dev mailing list