Example Ops- Client(Legal Entities ID)/Issue/Date/Application/INC#(If applicable)

**Key Notes for a new ticket**
- Put all key information in ZenHub Ticket Title, Title is the only searchable field in Zenhub
- Use Template when create a new Ops ticket
- Follow ZH Ops Ticket naming conversion : Client(Legal Entities ID)/Issue/Date/Application/INC# (If there is a ServiceNow ticket)
- Summarize issue, screenshot is highly preferred, copy and paste email content into ticket

**Contact information**
- Staff Name:
- Staff Email:
- Team Lead:
- Senior Analyst: (i.e Debbie)

-----------------

#### Issue Description

**PPR Search/Registration issue** – staff obtain the following info from client:
- [ ] Client’s BCROS account name and account number
- [ ] Client contact info (name, email, phone number)
- [ ] Date and time of attempting to complete search/registration
- [ ] For PPR Search:
- [ ] Search type and criteria
- [ ] Email address where we can send the report
- [ ] For PPR Registration:
- [ ] Screenshots of every screen (all information entered in registration fields) NOT just of error

**BCROS account issue** – staff obtain the following info:
- [ ] Client’s BCROS account name and account number
- [ ] Client contact info (name, email, phone number)
- [ ] Relevant screenshots of error
- [ ] Description of the issue
- [ ] Proposes solution

**NRA issue** – staff obtain the following info from client:
- [ ] NR #
- [ ] Issue with screen shot’s if possible
- [ ] Indicated if client paid by Credit Card and provide proof of payment if no receipt in NR,

** or **
- [ ] Client’s BCROS account name and account number
- [ ] Client contact info (name, email, phone number)
- [ ] Date and time of attempting to submit NR if applicable

**Namex issue** – staff obtain the following info from client:
- [ ] NR #
- [ ] Issue with screen shot’s if possible
- [ ] Client Contact info, for call back when issue resolved, if different from NR contact info.
- [ ] Make comment in NR what issue is and that it has been reported.
- [ ] When INC# has been assigned, add to NR comments

**FAS** – staff obtain the following info from client:
- [ ] Error Messages & codes:
- [ ] If an error – description of what trying to do, what happened and what should have happened i.e. tried to file an annual report on ________ routing slip, said balance was wrong, but was correct
- [ ] Screen shots if possible
- [ ] RS #
- [ ] Fee code info

**Benefit Companies and Co-ops – Alterations & Data Fixes**
- [ ] Company number
- [ ] Screenshots of errors
- [ ] What the fix needs to be (this is what it needs to look like)
- [ ] Refence any similar past issues
- [ ] Contact Information

**Societies (This is legacy application, not applicable for ZH Ticket at this moment, will come soon)**
- [ ] Email to ITOP’s SBC_ITOperationsSupport@gov.bc.ca and cc Elizabeth.espinosa@gov.bc.ca
- [ ] Society Number
- [ ] Screenshots of errors
- [ ] Refund information (amount, name, address, tender type)
- [ ] Contact Information

-----------------

**Ops Process**
- Refer to **Zenhub - BC Registries Staff Dashboard Guid**: https://docs.google.com/document/d/11Qh7me7qr2eCRHlaQGAujtWYg0q8rU79/edit

Start by reviewing the issue body and the linked Zenhub - BC Registries Staff Dashboard Guide. No repository file, test, or entry point is identified, so first clarify whether this is meant to update project documentation or an operational ticket template. Done should be defined as an agreed, maintainable location and acceptance criteria for the requested guidance.

Written by the indexing model from the issue text.