DFE-Digital / DFE-Digital/check-performance-data

Data Egress - Admin Implementation AB#294553

Open
#244 1 comment 0 reactions 1 assignee View on GitHub

@ajs-uk-dev is already working on this.

Since Sep 14, 2026.

Dominant language
C#
Stars
0
Forks
1
Avg merge
19h 21m
Merged PRs (30d)
54

Description

AB#294553

Please note that the linked ADO ticket mentions running particular reports to get the data from Zendesk. This isn't how we will do this technically as 1) you can't run a report through the API and 2) by getting the data directly ourselves we don't have to rely on a report being defined and 3) the report may have formats that are problematic.

After the CheckingExercise has closed, all of the ChangeRequest records with Status Submitted:Committed will also have a CMSId which references the zendesk ticket id.

Us those CMSIds to query the Zendesk API and get all the tickets:

https://esfa-preprod.zendesk.com/api/v2/tickets/show_many.json?ids={id},{id},...,...

That endpoint has a limit of 100 ids in the ids query param, so batch up the requests if there are more than 100.

Of those tickets that come back, any that have a status of accepted or auto-accepted need to be included in the CSV output.

I have attached the PoC console app that I used to test the API and the CSV generation. This is throwaway code and is only meant as an example.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.