Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 486071

Summary:	Should we invalidate the CLA when a user changes their email address
Product:	Community	Reporter:	Eric Poirier <eric.poirier>
Component:	Website	Assignee:	Eric Poirier <eric.poirier>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	chris.guindon, mike.milinkovich, wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:

Description Eric Poirier

2016-01-18 16:50:19 EST

Should we invalidate a user's CLA if they change their email address since the it's part of it.

The PersonID would not change when the email gets changed but the email on record will not match with the new one.

Comment 1 Mike Milinkovich

2016-01-18 19:09:16 EST

One potential answer is....it depends.

If they are changing their email address because they've employment status has changed, then definitely the CLA has to be invalidated.

If they are simply changing their email address for personal reasons then an alternative would be to provide a UI to do so. Of course, that takes effort on our part so invalidating it could be a temporary solution even if we want to allow it in the future.

Comment 2 Wayne Beaton

2016-01-18 20:56:34 EST

So, the email address isn't the trigger, it's the employer change that's the trigger.

If editing the email address in the CLA is desirable, doesn't it make sense to just not store the email address with the CLA and leverage the system's existing ability to manage and modify the email address?

I believe that in our original requirements, the signed CLA was to be immutable.

Comment 3 Eric Poirier

2016-01-19 09:33:34 EST

(In reply to Wayne Beaton from comment #2)
> So, the email address isn't the trigger, it's the employer change that's the
> trigger.

Should we invalidate automatically the CLA when the user state that the employer have changed?

> If editing the email address in the CLA is desirable, doesn't it make sense
> to just not store the email address with the CLA and leverage the system's
> existing ability to manage and modify the email address?

That could be a good way to do that. We could retrieve the email from the People table if necessary or create a new email column in the PeopleDocument table.

> I believe that in our original requirements, the signed CLA was to be
> immutable.

We also store the user's Legal Name that can be changed in the My Account section. Is this something we should remove from the CLA blob as well?

Comment 4 Christopher Guindon

2017-03-20 11:16:37 EDT

*** Bug 513595 has been marked as a duplicate of this bug. ***

Comment 5 Christopher Guindon

2019-02-19 16:44:37 EST

We recently had a discussion about this and we concluded that an email change does not require an invalidation of the ECA.

The reasoning for this is that the user ID will not change and as long as the system is tracking all the changes that take place; we have the necessary tracking to defend if required.

Comment 6 Christopher Guindon

2019-02-19 16:45:49 EST

(In reply to Christopher Guindon from comment #5)
> We recently had a discussion about this and we concluded that an email
> change does not require an invalidation of the ECA.
> 
> The reasoning for this is that the user ID will not change and as long as
> the system is tracking all the changes that take place; we have the
> necessary tracking to defend if required.

Wayne, please re-open if you disagree with this statement.