Update CAIA Tickets and How To Use Them.md

department-of-veterans-affairs · Oct 14, 2024 · 2090fa2 · 2090fa2
1 parent b2f041d
commit 2090fa2
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/teams/CAIA/Ops/CAIA Tickets and How To Use Them.md b/teams/CAIA/Ops/CAIA Tickets and How To Use Them.md
@@ -56,8 +56,8 @@ This section contains field data that is important for filtering and tracking is
   - sitewide accessibility
   - CAIA translation 
   - CAIA-a11y-research (used to denote CAIA research involvement for Assistive Technology support)
-- **Opened Date** - the date the ticket was created - this is auto generated by Github, however, the default data cannot be used to filter issues on the board
-- **Closed Date** - the date the ticket was closed - when closing a ticket, be sure to fill out this field (for content tickets, Lily will add this)
+- **Opened Date** - The date the ticket was created. This is auto-generated by Github, but the default data cannot be used to filter issues on the board, so we still need to manually input this date.
+- **Closed Date** - the date the ticket was closed. This is not auto-generated, so please be sure to fill out this field when you close a ticket (for content tickets, PDM will do this).
 - **Estimate** - the level of effort we think will be required for a ticket. Only used on Task tickets, not Epics. Level of effort is determined using basic tee shirt sizes based on the time it would take to complete the work iteself (not including waiting on SMEs or stakeholders, back and forth with OCTO, etc.):
   - **Small** for 1-5 days - Redirects, deprecating a page
   - **Medium** for 2-4 weeks - Best bets, React Widgets
@@ -106,6 +106,10 @@ The ticket status shows where work is in the CAIA pipeline and provides an overv
  -  **Closed** - work completed for this issue. Updates are live, the product has launched, or feedback or deliverables have been provided to the team.
   - **OCTO Audits** - tickets created by OCTO leadership - usually audit work
 
+# Closing tickets
+The way we close tickets matters to our reporting, but we have different steps to complete due to the range of ticket types and discipline setups on our team. 
 
-
-
+### Closing work tickets
+A11y: Individual contributors are responsible for closing tickets they are assigned to and tracking them in the reporting spreadsheet
+IA: Individual contributors are responsible for closing tickets they are assigned to and tracking them in the reporting spreadsheet
+Content: Individual contributors are responsible for moving tickets they are assigned to into validate. The PDM will track them in the reporting spreadsheet.