Fog Creek Software
Discussion Board




Resolved FogBugz cases not re-assigning to opener

When User A enters a bug, and User B resolves it, the case stays assigned to User B.  User B must manually re-assign the case to User A for verification.

Brian Herron
Monday, October 18, 2004

On the trial, the windows version,  or the php version?

Can you repeat this?

Michael H. Pryor
Fog Creek Software
Monday, October 18, 2004

I'm not sure.  It is the ASP version.

FogBUGZ Version 3.1.9 (DB 328)

Brian Herron
Monday, October 18, 2004

I can't reproduce this.  Are you able to reproduce it?

Michael H. Pryor
Fog Creek Software
Monday, October 18, 2004

We have two servers running FogBugz.  They are both the same version / build number (as listed above).

One machine resolves cases properly, the other leaves resolved cases in the original user's inbox.  It is reproducible and seems to be consistent.  I will try with other projects / users.

Brian Herron
Monday, October 18, 2004

Upon inspection we have limited it to a specific project.

We are trying each of the 4 areas for that project now.

Brian Herron
Monday, October 18, 2004

Areas have no impact, the entire project won't resolve properly.  The project name is 2 four words strings containg [A-Z] seperated by a single space.

Brian Herron
Monday, October 18, 2004

Is the primary contact for that project valid?  Are you getting script errors on that page?

Michael H. Pryor
Fog Creek Software
Monday, October 18, 2004

Please speak with Olivier Dagenais at your company, he has been making changes to the source code.

Dmitri
Fog Creek Software
Monday, October 18, 2004

Our FogBugz admin just went and verified that the primary contact's (the FB admin) account was valid by going to the admin's project link and clicking on his name.  His account was displayed, and all the information looked valid.

Our most recent 2 test scenarios were as follows:

User A logs in and creates 3 cases
case a) assigned to the default contact
case b) assigned to User B
case c) assigned to User A

User B then proceeds to resolve all 3 bugs.  There are no visible JS errors.  All 3 bugs remain assigned to the original assignee.

On a side note, some user's have been receiving intermittent errors:
There was an error with your request. Please fix the problem described below and hit back to resubmit your request.
Your bug was NOT submitted. Please hit back and resubmit your bug.: Invalid procedure call or argument

But that isn't consistent, and hasn't occured yet during our testing.

However once a user starts receiving it, they get it consistantly.  We are unsure how to make it go away, but it does eventually.

Brian Herron
Monday, October 18, 2004

You're using modified code. We have no way of knowing the changes that have been made, so I'm afraid we are not able to provide support. You can easily run setup to get back to the original source code. Or perhaps Olivier can roll back the recent changes that caused these bugs.

Dmitri
Fog Creek Software
Monday, October 18, 2004

Thanks Dmitri, you were correct.  Olivier did make custom code changes.  Unfortunately for us, Olivier is no longer available. 

Realizing that is was custom code pointed us in the correct direction, and we were able to resolve the problem.

Thank you for your assistance.

Brian Herron
Tuesday, October 19, 2004

*  Recent Topics

*  Fog Creek Home