Unintended modifications on imported tickets | Community
Skip to main content

Unintended modifications on imported tickets

  • April 3, 2024
  • 6 replies
  • 0 views

Hi
These are bugs I see on the ticket import api, ref:
https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_import/#ticket-import

 

  1. Signature is applied to all comments where agent is comment author
    1. This seems strange as comments usually have a signature from before, which results in double signature
  2. SLA metrics are generated for imported tickets
    1. See below JSON extract for an imported ticket (4 years old) that has its full resolution time set to today?

{

  "solved_at": "2020-05-28T08:23:26Z",

  "latest_comment_added_at": "2024-04-03T11:12:37Z",

  "reply_time_in_minutes": {

    "calendar": null,

    "business": null

  },

  "first_resolution_time_in_minutes": {

    "calendar": 635861,

    "business": 393941

  },

  "full_resolution_time_in_minutes": {

    "calendar": 635861,

    "business": 393941

  },

  "agent_wait_time_in_minutes": {

    "calendar": 0,

    "business": 0

  },

  "requester_wait_time_in_minutes": {

    "calendar": 0,

    "business": 0

  },

  "on_hold_time_in_minutes": {

    "calendar": 0,

    "business": 0

  }

}

 

 

6 replies

Tipene
  • April 9, 2024
Hi Lars,
 
Thanks for getting in touch!
 
Can you let me know if you're using the archive_immediately parameter and are still observing these behaviors? Or are the tickets being imported in a different status?
 
Thanks,
 
Tipene

  • November 4, 2024

When using the Ticket Bulk Import endpoint, I am also seeing all public comments from agents automatically apply the default Agent Interface signature.  This is not expected and is not wanted.  

 

Ticket status is primarily ‘closed’ but all statuses are present for one or more tickets.  I am not setting archive_immediately, nor do I want to do so. 

 

Is there a way to inhibit this behavior other than deleting the active Agent Interface signature setting?


Tipene
  • November 25, 2024
Hi James,
 
Sorry for delay in someone getting back to your here!
 
Would you be able to run a test import where you see this behaviour on your end so I can take a look at the logs for the request?
 
Thanks,
 
Tipene

  • January 16, 2025

Hi Tipene - I would be glad to do so.  This is still happening and I can run a test import at any time.  Thanks!


  • February 5, 2025

Tipene, apologies for the long delay in replying.  Please let me know we should connect to run a test import to demonstrate the behavior.  I have verified that it is still happening.  Thanks,

James


Greg29
  • March 7, 2025

Hi James! Feel free to run that whenever you'd like and then just let me know the approximate UTC time that you started that!