Change user email doesnt change associated tickets?

[atDev]

Why when you change a users email it does not cascade that database update changing the email field for any tickets owned by that user? Its annoying having to go into the database and do this manually.

[supportskins]

This should be added, as of now you will have to manually change the email address of all the first post created by the user in all the tickets he created. It can be a pain especially if the user has created numerous tickets.

[atDev]

True. And its not going to happen if a user has 100 tickets. That is a complete waste of time.

[atDev]

Whats the status on this?

[Jamie Edwards]

Moved to Feature Requests, and will be reviewed soon.

[atDev]

Originally Posted by Jamie Edwards

Moved to Feature Requests, and will be reviewed soon.

Are you sure this would be considered a feature request? If a users email is changed those tickets pretty much go in "limbo" as far as a user owner goes? Seems more like a bug.

[Jamie Edwards]

It is indeed a feature request, but being a fundamental one I think there is no question that it is needed. It may even be considered for a V3 release, I will discuss this with the developers.

[atDev]

Originally Posted by Jamie Edwards

It is indeed a feature request, but being a fundamental one I think there is no question that it is needed. It may even be considered for a V3 release, I will discuss this with the developers.

Can you explain why it would be a feature request and not a bug?

[Jamie Edwards]

Simply because it is working as designed - there is no attempted or existing attempt at an implementation of this feature (to cascade the database and ticket entries) which has broken (which would render it a bug); therefore I believe it exists as a feature request.

Granted, though I do agree this is a design flaw.

[Jamie Edwards]

Issue title: Change user email does not update tickets
View: http://bugs.kayako.com/index.php?cmd=view&id=76

Fixed

[richm]

Hi Jamie,

Can an additional field be added to bug tracker to indicate a patch is available for current stable release?

Unless I'm missing it, I'm having a hard time telling in the bug tracker when a bugs indicates "fixed" if there is a patch available or not. This could save us time in opening tickets and requesting patches if they are not available in current stable (assuming some things may have to wait for next stable)

Rich

[atDev]

Originally Posted by rixm

Hi Jamie,

Can an additional field be added to bug tracker to indicate a patch is available for current stable release?

Unless I'm missing it, I'm having a hard time telling in the bug tracker when a bugs indicates "fixed" if there is a patch available or not. This could save us time in opening tickets and requesting patches if they are not available in current stable (assuming some things may have to wait for next stable)

Rich

I agree. I realize you have the bug tracker, changelog, and then build comments from the user area but it seems like there is not a defined list of the version number and what was changed in that version number. I am thinking perhaps the changelog needs to be reorganized by version number rather than date.