Everything I've built and shipped.

Whole engagements scaffolded in one click

A manual trigger on a template ticket generates the entire structure for a new piece of work, then deletes its own trigger ticket so nothing is left behind.

• A full advertising iteration builds one epic plus 28 child tickets, half-iterations run off their own variant
• A website engagement builds a five-phase delivery checklist, from onboarding and audits through discovery, content, design, and technical architecture
• A new contract builds a standardized onboarding epic covering operations, branding, marketing, and hours reporting, with documentation links and due dates already set

A new engagement is stood up in seconds, structured identically every time, instead of a manager hand-building dozens of tickets.

Recurring work that schedules itself

Anything that repeats was moved off human memory and onto a rule.

• Monthly and quarterly ticket sets generate against the right account component, opening two weeks before they are due
• Date-window queries roll quarterly check-ins forward automatically, so each quarter's tickets appear without anyone creating them
• The monthly newsletter clones from a template with account fields filled in on the fly
• Five recurring team syncs generate weekly, and eight company holidays generate four weeks ahead

Nothing recurring depends on someone remembering it.

Quality gates enforced by the system

Review standards stopped being a convention people had to follow and became something the tracker applied on its own.

• Every new ticket receives a QA checklist on creation, with the ticket types that should not have one excluded by rule
• Reopening a ticket resets its completed checklist items so re-review starts clean instead of inheriting old ticks
• Moving a ticket to Ready for QA adds two days to the due date, so review has real room rather than eating the deadline
• Epics still open at the twelve-month mark transition to Ready for QA automatically

Escalation that fires before work goes late

Notifications target the one person who can act, in the channel they already live in.

• The assignee is alerted when a ticket sits in Ready for QA longer than 24 hours, and again when it goes overdue
• Users are alerted when they are mentioned in a ticket comment
• The reporter is warned when time is about to be logged past the remaining estimate, or when an original estimate is changed

Field-dependency enforcement with accountability

A scripted listener that catches incomplete ticket configuration and routes it to the person responsible, instead of into a queue nobody reads.

• Detects tickets missing the required sprint, assignee, and due-date combinations
• Reads the ticket changelog to work out who last edited those fields, then names them in a comment listing exactly what is missing
• Posts to Slack behind a recency check, so a burst of edits cannot spam the channel

Bad data gets corrected by the person who created it, usually the same day.

Stand-ups generated and delivered

A scheduled script that replaces the daily status round-trip.

• Direct-messages every team member each morning with their Blocked, In Progress, Overdue, and Due Today tickets
• Arrives in a ready-to-post format with clickable ticket links and due dates
• Skips anyone with no active work, so the message only lands when it is worth reading

Intake forms wired straight through to tickets

Requests that used to arrive as email now enter the system as tracked work.

• A time-off request form logs to a response sheet and opens the corresponding ticket
• A client support request form logs to a sheet, opens a ticket, and notifies the team in Slack
• Both were built as custom scripts against the form responses rather than off-the-shelf connectors

Requests stop living in inboxes and start carrying an owner and a due date.

Reporting leadership can act on

Scripted pulls that turn tracker and time data into the numbers the business actually runs on.

• A weekly client utilization report computing billable hours per client and burn rate against contracted hours
• An overview of active tickets, statuses, and workload across the team
• Ticket health monitoring that flags overdue, stale, and SLA-breaching items and reschedules where appropriate
• Reopened tickets exported on a schedule so rework can be reviewed as a trend, plus a subscription tracker reconciling accounting data against the card each one bills to

Paid tooling replaced with code I own

Two workflows running on a third-party automation platform were rebuilt in-house.

• A calendar integration that watches an eight-person meeting calendar set and creates tickets from the events on it
• A meeting-transcript sync that lands summaries and action items onto the right tickets
• Both rewritten as maintained scripts rather than vendor-hosted flows

The workflows became things the team could read, debug, and change without a subscription in the way.