Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem with object_before_set #2

Open
GoogleCodeExporter opened this issue Apr 8, 2015 · 0 comments
Open

problem with object_before_set #2

GoogleCodeExporter opened this issue Apr 8, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

If I update the Cc list for a component, it triggers the object_before_set 
function which tries to re-create an "Assignee" from the default assignee.
As this object already exist, it makes the function fail and report a double 
entry in the database.

The same problem occurs if I want to change the default assignee through this 
form to be another member of the assignee list, as the object already exist...

Attached is a quick and dirty fix to test 'newowner' is not already defined in 
the Assignee list and is different from 'oldowner'. In this case there is no 
need to create the Assignee object.

Original issue reported on code.google.com by [email protected] on 25 Sep 2012 at 9:09

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant