Use default event state and contacts when copying events
Sometimes when copying an event it makes sense not to copy it exactly. Most of the information in the copy should be the same as the original--but the event state and the requestor/scheduler should be the user's defaults, as if the event was being created from scratch.
Other times it does make sense to copy an event exactly, so this should be a configurable option.
Comments: 3
-
11 Oct, '22
Leonard BrettonWith the recent change on the contact fields (9/15/22 update) where the requestor changes to the current user this has created extra step for high volume schedulers that manually copy events. I think admins would like the option to choose whether the requestor is the original requestor or the current user. This could be preference setting that would allow users/ admin to choose which requestor is brought over during copying. Often it is the scheduler/power users that copy events and their contact becomes the requestor. The requestor field is still relevant in these cases. If not careful this can affect email scenarios where automatic emails are sent on save and requestor field is not changed to the proper requestor sending emails back to the scheduler.
-
13 Oct, '22
Bob EastmanLeonard's comment checks out. I can't believe removing the requestor was considered an "improvement". Please, at least give us a choice!
-
17 Apr, '23
Elizabeth SaltonJust tacking on to this, Iowa State University prefers to have the requestor stay the same for copy and relate events. Making this a configurable option makes sense.