Ricerche recenti
Nessuna ricerca recente

Radu Vaudva
Data ingresso 16 ott 2021
·
Ultima attività 03 gen 2023
Seguiti
0
Follower
0
Attività totali
8
Voti
4
Abbonamenti
2
PANORAMICA ATTIVITÀ
BADGE
ARTICOLI
POST
COMMENTI NELLA COMMUNITY
COMMENTI AGLI ARTICOLI
PANORAMICA ATTIVITÀ
Ultima attività di Radu Vaudva
Radu Vaudva ha commentato,
Subscribing to this as well, same use case as everyone else where tickets come in from partners on noreply@domain.com support@domain.com etc and we need to change the requester for these programatically.
Visualizza commento · Data ultimo post: 03 gen 2023 · Radu Vaudva
0
Follower
0
Voti
0
Commenti
Radu Vaudva ha commentato,
I've followed the recipe to create a ticket volume forecast based on created month (including the year at the top to resolve the "missing_year" issue but I am running into another issue I can't get around, which is "You need to have data for at least 2 cycles to forecast your result. Your current cycle length is 1". I see others have as well, but no solution was presented for it. Here's my set up, how do I fix this? I want to see the forecast for the next 6 months based on the past 6 months of data.
Visualizza commento · Data ultimo post: 09 lug 2021 · Radu Vaudva
0
Follower
0
Voti
0
Commenti