Was hoping someone could please help me out! We have a few individuals doing QA for our release -although they imput the bugs (and so OWN the bugs) they are not the ones responsible for assigning the bugs to the developpers - this appears to create a problem in that no emails are sent out (and an error is logged) if someone other than the owner or developper alters the bug. Does anyone know of a work around for this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, I checked that and STRICT_UPDATING is set to no and anyone CAN alter the bug, however if someone other than the reporter/developper changes something, an error/warning is logged in the error_log file and no emails are sent out - but the bug is changed in the database. If either the reporter or the develpper alter the bug no error is logged and emails are sent???
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Was hoping someone could please help me out! We have a few individuals doing QA for our release -although they imput the bugs (and so OWN the bugs) they are not the ones responsible for assigning the bugs to the developpers - this appears to create a problem in that no emails are sent out (and an error is logged) if someone other than the owner or developper alters the bug. Does anyone know of a work around for this?
Make sure that the STRICT_UPDATING configuration varialble is set to No. This should allow anyone to update the status of a bug.
Yeah, I checked that and STRICT_UPDATING is set to no and anyone CAN alter the bug, however if someone other than the reporter/developper changes something, an error/warning is logged in the error_log file and no emails are sent out - but the bug is changed in the database. If either the reporter or the develpper alter the bug no error is logged and emails are sent???
Any ideas?
I'll have to look into it a bit more. Would you mind creating a bug for this?