Show Menu
Cheatography
  1. Home >
  2. Cheat Sheets >

LT D2 Team Guide Cheat Sheet (DRAFT) by

This is a draft cheat sheet. It is a work in progress and is not finished yet.

JIRA Epic/S­tor­y/Task statuses

Dev backlog
Work not started. Pending planning of the task.
In progress
Implem­ent­ation in progress. Assigned to one of the developers.
Ideally max one issue in this status per developer.
In review
Implem­ent­ation complete but in code review. Waiting for acceptance from tech leaders. Assigned to one of the tech leaders.
On hold
Implem­ent­ati­on/­testing has been in progress, but currently on hold. Keep assigned.
Ready for QA
Implem­ent­ation complete and reviewed. Waiting for testing. Assigned to one of the testers.
In QA
Testing in progress. Assigned to one of the testers.
Ideally max one issue in this status per tester.
Ready for deployment
Both implem­ent­ation and testing complete. Return to owner.
Deploy­ed/­Closed
Deployed in pre-pr­odu­ction environment.
Ideally deployed in production
Rejected
The task was cancelled or rejected. Return to owner.
These describe the lifecycle statuses of a major item in JIRA. It is important to follow up the workflow as it helps to organize the work and keep track on the tasks.

JIRA Sub-task statuses

To do
Work not started yet.
In progress
Work is in progress.
Done
Work is done.
Rejected
Work is cancelled or rejected.
These statuses are used for develo­per­s/t­esters in JIRA sub-tasks to break the bigger tasks into smaller chunks of work. The sub-task resembles a logical organi­zation of work.
A task is to create a user web service. A set of sub-tasks could be:
Design SQL data model
Code DAO/Re­pos­itory objects
Code a REST endpoint using DAOs
Write unit and integr­ation tests
  

JIRA worflow explained

1. When you start implem­ent­ation, set status to In progress
2. When you pause implem­ent­ation, set status to On hold
3. When you resume implem­ent­ation, set status to In progress
4. When you switch assignee during implem­ent­ation, set status to On hold and assign issue to the other developer
5. When you complete implem­ent­ation, set status to In review
6. When review has been approved, set status to Ready for QA and assign issue to a respon­sible tester
If no respon­sible tester, ask for one in testers team
7. When you start testing, set status to In QA
8. When you pause testing, set status to On hold
9. When you resume testing, set status to In QA
10. When you switch assignee during testing, set status to On hold and assign issue to the other tester
11. When you find a defect during testing, set status to On hold and assign to the respon­sible developer
If no respon­sible developer, ask for one in developers team
12. When you complete testing succes­sfully, set status to Ready for deployment and assign to a release manager.
Current RM: Bartosz Adamik.
In case of an urgent production fix, set label to RC0