JIRA Status
@here, below are some example to follow up questions related to Issue Type = "STORY" - if you have questions/suggestion please comment ya.
===========================================================
Available Statuses from the Guide (https://docs.google.com/document/d/193X6DUbe5E6psCZNRd6Logbvvt4X04JQTc8ytA2XDH4/edit?ts=5ae53ef7#bookmark=id.t2s55tbeu8sl):
- To Do - not started yet
- Canceled - epic/story/task is canceled.
- In Progress - includes "design in progress", "design complete", "code in progress", ..
- Blocked - blocked by something
- Released to staging - ready for testing
- Testing & QA - indicates testing is in progress either by dev or QA
- QA Blocking - qa testing is blocked (e.g.: due to broken shared staging, ..)
- Ready for prod - testing is done, ready for release
- Delivered to Prod - released
- Reopened - used when a bug is reopened due to incomplete fix
===========================================================
BLOCKED:
Definition:
- Development done, but: waiting for code review (implication: normally story point is consumed).
- Development blocked - unable to continue because internal dependencies or external dependencies (implication: story point is not fully consumed and need adjustment for next sprint)
- Development done but unable to test (implication: normally story point is consumed)
- Not yet started but considered blocked due to un-clear requirement, internal/external dependencies are not completed.
- Follow Up Action:
- If needed please create another JIRA ticket internal team or external team that link to the blocked item
- Add "Team Note" section in the description to describe the reason of the story blocked.
- To easily identify and to be able to filter, please set the label like "blocked-review", "blocked-external", "blocked-not-testable"
RELEASED TO STAGING
Definition:
- Story has been tested and it is ready for testing either by QA or by Tester (PM, Eng)
- BE: deployed to staging or shared-stg and ready for test
- WEB: deployed to test server and ready for testing
- ANDROID/IOS: QA is ready to test the story
TESTING & QA
Definition:
- Testing in progress
- If issue found and its considered critical/major (blocked) or main acceptance criteria is not met, then send back the Story to "REOPENED", engineer then need to fix the issue
- If issue found can be considered major (but not block) or minor or trivial then create bug tickets
READY FOR PRODUCTION
Definition:
- BE: tested in shared-stg and ready for release (story considered as DONE)
- WEB: tested in test/staging server (story considered as DONE)
- ANDROID/IOS: main acceptance criteria is tested (story considered as DONE)
NOTE: When we end the sprint, Story that are not DONE will be excluded and either go back to Backlog or Move to next sprint. To easily see what are the blocked story, I will create another board ya.