Bugs

All 3 open Endeavour lotteries as at 03/06/21 have thousands of tickets missing from the mail ticket data files for the print house. There is also no way for us to confirm the data file is accurate and includes all relevant ticket sales due to the encryption process.

EF's Star supporters are having to be carefully managed in terms of changes to their membership in the platform due to the impacts the changes are having at time of draw. Specific examples have been forwarded to Naren, however being no changes can be made to an existing membership and a new membership needs to be created, if completed in the system, it could exclude a Star supporter from draws they have valid tickets in. EF see this as a bug as valid tickets are easily excluded from draws through accurate updates made to supporter accounts.

With EF's Star Supporter Loyalty program, members are misusing the website to remove credit cards from their account. They see this as a way to cancel/pause their membership, even though it is not. Unfortunately this practise has led to approx. 400 supporters doing this since EF's go live. The main issue here is that other cards are being selected to cover loyalty program payments. We have instances where we have a husband and wife on the account. He removed the CC from his account assuming this is cancelled. She went online a few weeks later, purchased an adhoc ticket, not part of SS membership, and PBJ software automatically used this card to update the SS membership and reinstate it. We have no authority to do this from the supporter. This also occurs for anyone else who uses a different card on an adhoc purchase after removing the original. Examples can be provided if need be, please speak with Wyland. Thanks, Kirsty

Currently when creating an account the validation prevents a user or operator from registering with a DOB making the supporter under 18 or over 105. However, this validation isn't present when updating an existing account. Could we please have this validation standardised to prevent DOB being updated to invalid values?

When trying to edit a supporters details with a unit number that contains a alpha character the address is flipped. I have included screenshots that show the address being added and the resulting address. FYI - this job has been logged previously. However, it was merged with PO BOX Address formatting, but was not fixed when this was completed.

There is an issue when export/downloading customer searched data that removes the applied filter. e.g. When using the customer search function and applying date range filter to locked accounts - cannot download data as it removed the date filter and outputs all previously locked accounts.

At times we have a need to remove an email address from a supporters account (they may no longer use that address and do not supply a new one, they may have been sharing an email and that is no longer appropriate etc.). This is not allowed in the UI regardless of whether the supporter meets validation through other fields or not.

App push notifications are only delivered to supporters who are actively logged into their mobile app, not all supporters who have agreed to receive app push notifications.

When selecting an activity preferences under preferences "no answer" and "said no" if selecting the option BEFORE adding a note the pop up closes. So note needs to be added before option selected. Seems backwards with the flow of the form.

When adding a note to preferences "No Answer" or "Said No" the system duplicates the "preference" in the Customer Activities. e.g. Customer did not answer phone: Customer was phoned but did not answer.