Recherches récentes
Pas de recherche récente

Radu Vaudva
Adhésion le 16 oct. 2021
·
Dernière activité le 03 janv. 2023
Suivis
0
Abonnés
0
Activité totale
8
Votes
4
Abonnements
2
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Radu Vaudva
Radu Vaudva a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 03 janv. 2023 · Radu Vaudva
0
Abonnés
0
Votes
0
Commentaire
Radu Vaudva a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 09 juil. 2021 · Radu Vaudva
0
Abonnés
0
Votes
0
Commentaire