Búsquedas recientes
No hay búsquedas recientes

Radu Vaudva
Incorporación 16 oct 2021
·
Última actividad 03 ene 2023
Seguimientos
0
Seguidores
0
Actividad total
8
Votos
4
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Radu Vaudva
Radu Vaudva hizo un comentario,
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.
Ver comentario · Publicado 03 ene 2023 · Radu Vaudva
0
Seguidores
0
Votos
0
Comentarios
Radu Vaudva hizo un comentario,
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.
Ver comentario · Publicado 09 jul 2021 · Radu Vaudva
0
Seguidores
0
Votos
0
Comentarios