Finding a bad ticket within Footprints

Modified on Sat, Jun 29, 2024 at 11:51 AM

Everything is crashing and burning how do I find the ticket responsible?!?!?!??!?


This is the 2nd time this has happened, so I made a program to help us with this and it can be found here: https://git.jpg.com/support/goldenticket

THE PROGRAM ONLY SUPPORTS INCIDENTS! IF YOU WANT TO ADD OTHER TICKET TYPES, GO AHEAD, MAKE A BRANCH THEN MAKE THE UPDATES

  • Make sure you have .NET 6.0 on your machine

  • Download and Unzip the Repo

  • Open the SLN

  • Build and Run the Project

  • Press '1' and let it run the searches

enter image description here

One of the Searches will fail, the program will tell you which one, and once you've identified which search has failed go to Footprints and Select Manage Searches

enter image description here

enter image description here

I've created searches that begin with [DEBUG] to help us with this and to find the searches quickly (Pending Release is somewhere else in this list).

Lets say the program failed on 'In Progress' Tickets. Run the In Progress search and then take a picture of the Records column ONLY

enter image description here

Once you have that picture, go to this website here: https://brandfolder.com/workbench/extract-text-from-image

Upload the image to this site and it'll extract the text for us

enter image description here

Copy this List and then Rerun the program, pressing Option 2 this time.

This will create a 'tickets.txt' within the same directory of the executable

enter image description here

Go to 'tickets.txt' and then paste the copied list there

Run the program again and press Option 2 again

This will now find us the Golden Ticket! Once you've found it let Bradley, Howard, or Christian know!

We see here that IN-164997 is the issue!

enter image description here

BYEEEEE (IYKYK)

enter image description here

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article