Cách Viết Jira Ticket Bằng Tiếng Anh — User Story, Task & Bug

1
2

Title: Fix bug
Description: (trống)

1
2

Title: Làm tính năng login
Description: Anh cần tính năng login, em fix giúp nhé

1

As a [role], I want to [action], so that [benefit].

1
2
3

Given [precondition]
When [action]
Then [expected result]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

Acceptance Criteria:

Given the user is on the login page
When they click "Forgot Password" and enter their email
Then they receive a password reset link within 5 minutes

Given the reset link is valid
When the user sets a new password (min 8 characters)
Then they are redirected to the login page with a success message

Given the reset link has expired (after 24 hours)
When the user clicks the link
Then they see an error message: "This link has expired"

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16

Title: [Verb] + [Object] + [Context]

Description:
## Objective
[What needs to be done and why]

## Technical Details
- [Detail 1]
- [Detail 2]

## Definition of Done
- [ ] [Checklist item 1]
- [ ] [Checklist item 2]

## Notes
[Any additional context]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

Title: Set up CI/CD pipeline for staging environment

Description:
## Objective
Configure GitHub Actions to automatically deploy the staging
branch to our AWS staging environment, reducing manual deployment
time from 30 minutes to under 5 minutes.

## Technical Details
- Create `.github/workflows/staging-deploy.yml`
- Use AWS ECS Fargate for container deployment
- Add Slack notification on deployment success/failure
- Environment variables stored in GitHub Secrets

## Definition of Done
- [ ] Pipeline triggers on push to `staging` branch
- [ ] Docker image built and pushed to ECR
- [ ] ECS service updated with new task definition
- [ ] Slack notification sent on success and failure
- [ ] Pipeline runs under 10 minutes
- [ ] Documentation updated in README

## Notes
- Reuse existing Dockerfile from production pipeline
- Staging DB credentials in AWS Secrets Manager

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

Title: [Component] — [Brief description of the bug]

Description:
## Environment
- Browser/Device: [e.g., Chrome 120, iPhone 15]
- OS: [e.g., macOS 14.2, Android 14]
- Environment: [staging/production]
- Version/Build: [e.g., v2.3.1]

## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Screenshots/Logs
[Attach evidence]

## Severity
[Critical / Major / Minor / Trivial]

## Additional Context
[Any other relevant info]

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

Title: Checkout — Payment fails silently when using Visa cards

## Environment
- Browser: Chrome 122 on macOS 14.3
- Environment: Production
- Version: v3.1.0

## Steps to Reproduce
1. Add any item to cart
2. Proceed to checkout
3. Select "Credit Card" as payment method
4. Enter a valid Visa card number
5. Click "Place Order"

## Expected Behavior
Order is processed and user sees confirmation page.

## Actual Behavior
Page reloads without any error message. Order is NOT created.
Console shows: `Uncaught TypeError: Cannot read property
'token' of undefined`

## Screenshots/Logs
- Console error: [screenshot attached]
- Network tab shows 500 error on POST /api/payments

## Severity
Critical — Affects all Visa card payments (est. 60% of transactions)

## Additional Context
- Mastercard payments work correctly
- Issue started after deployment on 2026-04-09
- Possibly related to Stripe SDK upgrade in PR #847

1
2
3

Update: Completed the database migration script.
Currently running integration tests.
ETA for completion: Tomorrow EOD.

1
2
3
4
5
6

@PM — Could you clarify the expected behavior when the user
has multiple addresses? Should we:
a) Use the most recent address as default, or
b) Prompt the user to select one?

This affects the checkout flow and estimated effort.

1
2
3
4
5

⚠️ Blocked: Cannot proceed with payment integration.
The Stripe API key for staging is expired.

Action needed: @DevOps please update the key in AWS Secrets Manager.
Ref: PROJ-890

1
2
3
4

Resolved in PR #523.
- Tested on staging ✅
- QA verified ✅
- Ready for production deployment.

1
2
3
4
5
6

As a [___], I want to [___], so that [___].

Acceptance Criteria:
Given [___]
When [___]
Then [___]