[CAL-118] Ability to include additional fields in event title
Is your proposal related to a problem?
No
Describe the solution you'd like
When using additional feeds on an event type it should be possible to include the field in the event title. For example:
"Matt:{ATTENDEE} re {SUBJECT}" where "Subject" is the name of the additional field
Describe alternatives you've considered
Otherwise, this requires different meeting types for every potential subject to appear on the calendar invite.
Additional context
Hey @mattsmallman. So right now we have 4 types of additional fields: text, multiline text, number, checkbox. For text and number it would be pretty straightforward to think about including it in the event title. How about multiline text and checkbox? How would you see that working? Would love some feedback here so we create the best solution. Thanks in advance!
I only really want text in the subject but if the same field code is used elsewhere, then number and multiline might be helpful but I can't think of a use case for me right now. I'm assuming these fields are already available in your API/Workflows.
For context I have a generic set of 30,45,60 min appts which clients can book but because the content varies so much it's helpful for them to add a little more context to the subject line in addition to whatever notes they add. Otherwise it's hard for both parties to know what the meeting is about when glancing at their calendars.
@leog Same here, just text would be really helpful.
As an example, my event types all have a custom text field for Company. Being able to include that where I currently include {ATTENDEE} would be huge!
One more use case for this — I want to clarify meeting title (goal) for all participants. Because it's not so obviously why some guy invited me to some personal meeting. Otherwise I need to create a lot of different events types.
@CarinaWolli and @hariombalhara you have some experience with variables. any idea how we could add additional inputs into variables?
Should be possible to include additional inputs as variables for the event name. I will take a look at that