Posted: February 8, 2024 at 12:47 pm
I’m still extremely frustrated with the process of creating new datetimes and tickets. It’s so convoluted that I can’t tell half the time if I’m making a mistake or there’s a bug. I have an expired event, I wanted to create a new datetime and ticket for it, so I turned off the filter showing only upcoming events, and then I copied an expired datetime, and changed the date on the newly created one. Then I assigned it to an expired ticket. Then I copied the expired ticket to a new ticket and edited the new ticket and reassigned the datetime to this new ticket. The problem is, when I look at the Ticket Assignment manager for Datetime ID 1818 it still shows the original expired class date https://app.screencast.com/LhIbDPAIrvX5U, even though when I look at the list, and I can see both, ID 1818 has the correct date: https://app.screencast.com/M6ZJyfDxLwtOu. This type of inconsistency seems to happen a lot when I’m doing this and it causes me a lot of wasted time checking and rechecking things, and then I never feel confident that it’s all correct. Isn’t there a better way?
My apologies for the delayed reply here.
So it looks like the Ticket Assignment Manager (TAM for short) isn’t updating with the changes to Datetimes made on the current page load.
To work around that, after you create the Datetime and Ticket and set the values you want to use on those, refresh the page before opening up TAM so it loads with the latest changes made.
I’ve created a ticket for our developers to investigate this further.
Duplicating a current DateTime (and ticket) to then reassigning is the quickest way to create a new DateTime/Ticket pair within EE currently. You could use the ‘Add Date’ button to create a new DateTime, set the values and then assign that to an expired ticket before creating the new ticket and re-assigning but it’s slower than duplicating a current DateTime.