Calendar week 52


  • Sydney Neubauer

    We definitely had this issue affecting our reports. Upvoting

  • Anton M.

    upvoting. having 2 weeks №52 in one year is a mess (Jan from previous year + Dec for current)  .
    In our internal reports I've created a new custom metric as a workaround. 

    Here is calculated attribute code, that works for ticket creation week and year. It uses the fact, that first day of the week only exists in 1 year, + some formatting, so the text field will sort correctly. 

    If WEEK_NUMBER_MONDAY(START_OF_WEEK_MONDAY([Ticket created - Timestamp]))<10 then 
    String(Year(START_OF_WEEK_MONDAY([Ticket created - Timestamp])))
    +"-0"+String(WEEK_NUMBER_MONDAY(START_OF_WEEK_MONDAY([Ticket created - Timestamp])))

    String(Year(START_OF_WEEK_MONDAY([Ticket created - Timestamp])))
    +"-"+String(WEEK_NUMBER_MONDAY(START_OF_WEEK_MONDAY([Ticket created - Timestamp])))

    PS you may need to use WEEK_NUMBER_SUNDAY if your weeks start on Sunday. 

  • CJ Johnson

    Last year the problem was week 53, forgot about this particular issue but agreed, it would be nice not to have to work around this every January. 

  • Kirill Akimov

    We also have the same issue, Zendesk team!

  • Brad Harris

    Same. It's Feb, 2023 but we're seeing Week 52 2023 at the end of all of our column charts.

  • Eugene Orman
    Zendesk Product Manager

    Kirill Akimov & Brad Harris, have you tried using the Year and week attribute instead of the Week of year?

    Here is an example:

    Let me know if this attribute will help to resolve the issue with Week 52.


Please sign in to leave a comment.

Powered by Zendesk