Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepend or Append Descriptor to Generated Ticket Names #1157

Open
garthkoyle opened this issue Mar 3, 2022 · 4 comments
Open

Prepend or Append Descriptor to Generated Ticket Names #1157

garthkoyle opened this issue Mar 3, 2022 · 4 comments
Assignees
Labels
C: UI/UX 🚽 category D: REM ♺ domain: Recurring Events Manager P2: HIGH priority 😮 priority: high S2: planning 📋 status T: refactor 🛠 type: MOD - changes in existing functionality

Comments

@garthkoyle
Copy link

When a new series of tickets are created, they all have the same name. It would be nice to allow people to append something at the beginning or end of the ticket that indicates something... Such as the date of the associated ticket, or the datetime name of the associated ticket. Maybe we can give people a few shortcodes to parse?

Otherwise people can change the dates manually.
image

@tn3rb tn3rb transferred this issue from eventespresso/eea-recurring-events-manager Jun 20, 2022
@tn3rb tn3rb assigned majidabbasi96 and unassigned tn3rb Jun 20, 2022
@tn3rb tn3rb added T: refactor 🛠 type: MOD - changes in existing functionality D: REM ♺ domain: Recurring Events Manager S2: planning 📋 status C: UI/UX 🚽 category P3: med priority 😐 priority: medium labels Jun 20, 2022
@garthkoyle
Copy link
Author

Rather than editing the ticket name, perhaps this is a template control option in REM or EE that just modifies the display for the front-end and back-end? A template control might make it more compatible with the Messages system.

@garthkoyle
Copy link
Author

Here is an example of the problem on the front-end:
image

@tn3rb tn3rb assigned tn3rb and unassigned majidabbasi96 Jun 30, 2022
@tn3rb tn3rb assigned majidabbasi96 and unassigned tn3rb Jul 19, 2022
@tn3rb
Copy link
Member

tn3rb commented Jul 19, 2022

@majidabbasi96
I'll add some additional details for you, so plz wait before adding any code
feel free to poke around in the files to familiarize yourself with things

@tn3rb
Copy link
Member

tn3rb commented Jul 19, 2022

In the REM Ticket Form Config, let's add a switch titled "Add Date to Ticket Name" immediately after the "Shared Ticket" switch, that only appears when that switch is toggled "OFF".

Prefix Ticket Name with Date - Switch

which when clicked shows a row with two select boxes:

  • one for choosing the date format
  • the other for choosing where to position the ticket name

Prefix Ticket Name with Date - Format

for now, let's populate the "Format" select with the following options:

  • Full Month Day Year (December 31 2099)
  • Short Month Day Year (Dec 31 2099)
  • Short Month Day (Dec 31)
  • WordPress Settings Date Format

values can be set using the actual date format codes (like M d Y or whatever) based on formats used by date-fns

and populate the "Position" select with:

  • Before Ticket Name
  • After Ticket Name

Because we do NOT want to add dates to names of shared tickets, we need to hide these options if "Shared Ticket" is toggled to true. To control the display of the form row with the format and position select boxes, you will need to set a predicate for the conditions. For example, in the same form config, clicking on the "Shared Ticket" switch will change the options displayed for the "Ticket Sales Start" and "Ticket Sales End" form sections, so you can use that same logic to control the new form row being added.

Upon submission, make sure the options get applied to the ticket template displayed on the REM Tickets step. Any date can be displayed (like the current date) as long as it uses the format and position that the user selected.

REM Ticket Templates

Upon submitting the final step of the REM editor, ticket names will need to include the date if that option has been enabled by the user. The date obviously has to come from the related datetime and should already be present in the ticket generation logic since it is used to calculate the ticket start and end dates for non-shared tickets.

@tn3rb tn3rb removed their assignment Apr 4, 2023
@tn3rb tn3rb added P2: HIGH priority 😮 priority: high and removed P3: med priority 😐 priority: medium labels Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: UI/UX 🚽 category D: REM ♺ domain: Recurring Events Manager P2: HIGH priority 😮 priority: high S2: planning 📋 status T: refactor 🛠 type: MOD - changes in existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants
@tn3rb @garthkoyle @alexkuc @majidabbasi96 and others