„It doesn't work“ nie je bug report — je to otázka, ktorá spustí ďalích päť callov. V medzinárodnom IT tíme bug po anglicky musí byť reproducible, testable a actionable. Tento návod je pre developerov, QA a support, ktorí popisujú alebo vysvetľujú chyby.
IT kontext: Angličtina pre IT. Blocker (nie bug): Ako vysvetliť blocker po anglicky. Meeting pri incidente: Meeting po anglicky.
Bug vs. blocker vs. incident
<a id="section-0"></a>
| Typ | Čo to je | Príklad |
|---|---|---|
| Bug | Chyba v softvéri | Login fails on Safari |
| Blocker | Prekážka tvojej práce | Can't deploy — no access |
| Incident | Produkcia down / kritický dopad | Payment API 500 since 14:00 |
Šablóna bug reportu (Jira / ticket)
<a id="section-1"></a>
Summary: Jedna veta — čo je zlého.
Steps to reproduce:
- Go to checkout page
- Add item to cart
- Click Pay with card
- Enter valid card details
- Click Submit
Expected result: Payment succeeds, order confirmation shown.
Actual result: Error message „Payment failed“ — no charge on card.
Environment: Chrome 120, macOS, staging, user role: customer.
Severity: High — blocks checkout on staging.
Attachments: Screenshot, log snippet, HAR file.
Severity a priority — frázy
<a id="section-2"></a>
- Critical / P0 — production is down, all users affected.
- High — checkout broken, no workaround.
- Medium — export fails but manual export works.
- Low — typo in footer on admin panel.
- Regression — this worked in v2.3, broken in v2.4.
Reproduction steps — dobré vs. zlé
<a id="section-3"></a>
Zlé:
- Payment doesn't work.
- Sometimes crashes.
Dobré:
- Reproduces 100% when cart has 2+ items with discount code SAVE10.
- Only on iOS 17 — Android works fine.
- Happens after session timeout — user must log in again.
Expected vs. actual
<a id="section-4"></a>
Vždy obe strany:
- Expected: Email sent within 5 minutes. Actual: No email after 30 minutes.
- Expected: Button disabled when form invalid. Actual: Button clickable, API returns 400.
Logs a technický kontext
<a id="section-5"></a>
- Stack trace attached — NullPointerException in OrderService.java line 142.
- Console shows CORS error when calling api.example.com.
- Request ID for correlation: req-abc-123 — check server logs around 14:02 UTC.
Slack — rýchlý bug alert
<a id="section-6"></a>
Heads up — bug on staging
Checkout fails after adding discount code.
Steps: cart → SAVE10 → pay → error.
Screenshot in thread. Ticket #4550 created.
Severity: high — blocking QA sign-off.
Incident call — 60-sekundový update
<a id="section-7"></a>
Šablóna pre calл:
We have an incident — payment processing failing since 14:02 UTC. About 15% of transactions affected. Root cause under investigation — suspect recent deploy. Mitigation: we're rolling back now. ETA for rollback: 10 minutes. I'll post updates in Slack #incidents.
Frázy počas incidentu:
- Impact: X users / Y% of traffic
- We're rolling back / deploying hotfix
- Root cause identified — misconfigured cache TTL
- Incident resolved — monitoring stable for 30 min
- Postmortem scheduled for tomorrow
Komunikácia s QA
<a id="section-8"></a>
QA hlási bug:
- Thanks — I'll pick this up. Reproduced locally.
- Can't reproduce — can you share video or exact timestamp?
- Closing as duplicate of #4498.
- Not a bug — documented behavior in AC ticket #4400.
Dev oznamuje fix:
- Fix deployed to staging — please retest ticket #4550.
- Hotfix in production — verify on your side.
Bug pre non-technical stakeholder
<a id="section-9"></a>
Jednoduchý jazyk — bez stack trace:
- Users can't complete payment when they use a discount code — we're fixing it today.
- The issue affects about 1 in 10 checkout attempts — not a security breach, just a logic error.
Viac: Technický problém s klientom.
Kompletný príklad ticketu
<a id="section-10"></a>
Summary: Checkout fails when discount code applied to multi-item cart
Description: When a user adds 2+ items and applies discount code SAVE10, clicking Pay returns „Payment failed“. Single item with same code works.
Steps:
- Log in as test user
- Add 2 products to cart
- Apply SAVE10
- Proceed to payment, enter test card 4111…
- Submit
Expected: Order completes, confirmation email sent.
Actual: Red error banner, order not created. No charge on card.
Env: Staging, Chrome 120, Windows 11
Severity: High
Precvičenie
<a id="section-11"></a>
- Napíš bug report pre reálný alebo fiktívny problém — plná šablóna.
- Skráť na 3-vetový Slack alert.
- Priprav 60-sekundový incident update nahlas.
- Vyskúšaj IT scenár — vysvetli bug v simulácii.
Súvisiace články
<a id="section-12"></a>
| Téma | Článok |
|---|---|
| Programátori | Angličtina pre programátorov |
| Klient | Technický problém s klientom |
| Support | Angličtina pre customer support |
Záver
<a id="section-13"></a>
Bug po anglicky = kroky, expected, actual, environment. Jedna jasná veta v summary, reprodukcia pre kohokoľvek v tíme a severity, ktorá zodpovedá dopadu. Tím opraví bug rýchlejšie než keď musí hádať, čo „doesn't work“ znamená.