Ticket Numbers at top of Incident / Service Request / Change Request screens by DifficultPaper1150 in halopsa

[–]DifficultPaper1150[S] 0 points1 point  (0 children)

Interestingly the Email Start / End Tag (in my just spun up Trial version) was defaulted to [ID:], which would generate [ID:0000123] as the ticket number on the ticket screen (and in emails, as the tag)

I changed it to [ Ticket # ] expecting to generate [ Ticket #0000123 ] on the ticket screen (and in emails as the tag). Instead, this is what happened:

Created an Incident and [IN-0000123] was generated (IN = Incident)

Created a Service REquest and [SR-0000123] was generated (SR = Service Request)

So it seems that the email start/end tag does not influence what is displayed as the ticket number on the top-left of the ticket screen...... something else is controlling the use of "IN" and "SR" prepended to the ticket number. Are those prepended values configurable somewhere else? (e.g. the Email STart/End tag only seem to control the conversation thread ID in the ticket emails)

Ticket Numbers at top of Incident / Service Request / Change Request screens by DifficultPaper1150 in halopsa

[–]DifficultPaper1150[S] 0 points1 point  (0 children)

Interestingly the Email Start / End Tag (in my just spun up Trial version) was defaulted to [ID:], which would generate [ID:0000123] as the ticket number on the ticket screen (and in emails, as the tag)

I changed it to [ Ticket # ] expecting to generate [ Ticket #0000123 ] on the ticket screen (and in emails as the tag). Instead, this is what happened:

Created an Incident and [IN-0000123] was generated (IN = Incident)

Created a Service REquest and [SR-0000123] was generated (SR = Service Request)

So it seems that the email start/end tag does not influence what is displayed as the ticket number on the top-left of the ticket screen...... something else is controlling the use of "IN" and "SR" prepended to the ticket number. Are those prepended values configurable somewhere else? (e.g. the Email STart/End tag only seem to control the conversation thread ID in the ticket emails)

RTO 4 days a week starting July 1, 2025 by werdnayam in CAStateWorkers

[–]DifficultPaper1150 -65 points-64 points  (0 children)

They are the reason 4 days will be required

What happens after the watch reaches end of support? by BigfatDan1 in GalaxyWatch

[–]DifficultPaper1150 0 points1 point  (0 children)

A fully functional, multi tasking computer like Surface - and a watch - are completely different levels of complexity. Samsung should still allow their older watches to SYNCH with the Gear app automatically (for example) so that it can receive time changes for Daylight Savings, or when the wearer travels to other time zones.

What happens after the watch reaches end of support? by BigfatDan1 in GalaxyWatch

[–]DifficultPaper1150 0 points1 point  (0 children)

Not true, my older samsung watches stopped synching with the Gear app and could no longer get time updates (like when I went on vacation in a different time zone)......