Git and GitHub for Product Managers
Writing an Issue Engineers Can Act On
If you're raising a bug, a well-written issue saves a round trip and often gets it fixed the same day. A vague one generates three clarifying questions and sits for a week.
A BUG ISSUE THAT GETS FIXED
TITLE
Scheduled payment skipped when date is the 31st
WHAT HAPPENS
A payment scheduled for the 31st doesn't go out in
months with fewer than 31 days. No error is shown.
WHAT SHOULD HAPPEN
It should be taken on the last day of that month.
That's what our help page promises.
HOW TO REPRODUCE
1. Set up a scheduled payment for the 31st
2. Wait for a 30-day month
3. Payment is silently skipped
EVIDENCE
3 support tickets in February: #8814, #8902, #8977
Account 44-2201 has it happening now.
IMPACT
Customers think a bill has been paid. Two of the
three reported a late fee from their supplier.
-------------------------------------------------
Six sections. The last two are the ones only a PM
can supply, and they're what gets it prioritised.
Evidence and Impact Are Your Contribution
Engineers can write the first four sections. They usually can't tell you how many customers hit it or what it cost them. Those two sections are the ones that move a bug up a queue, and supplying them is the most useful thing a PM does in an issue tracker.