Closed saimatsumoto closed 7 years ago
Thanks @saimatsumoto !
Please include your proposed changes in the description when they are ready for review!
@thescientist13 @kpisano I'd appreciate it if you can review this. Thank you!
@saimatsumoto from my perspective this looks great and will be really helpful to have in the onboarding guide. @thescientist13 may have more technical thoughts. Thanks!
@saimatsumoto I think a couple good things to add would be the ownership of transitioning an issue into each state and ensure proper assignee roles. I think it might be good captured as table?
STATE | Who Should Transition | Assignee |
---|---|---|
TODO | N / A | Contributor |
IN PROGRESS | Contributor | Contributor |
IN REVIEW | Contributor | Team Lead |
TEST | Team Lead | Tester / Product Owner |
DONE | Tester / Product Owner | Tester / Product Owner |
@thescientist13 That looks great and more intuitive. Thank you for the great tip!
State | Who Transitions | Assignee | Status |
---|---|---|---|
TODO | N/A | Contributor | Task within the sprint; development did not start |
IN PROGRESS | Contributor | Contributor | dev work is initiated and in progress |
IN REVIEW | Contributor | Team Lead | dev work is completed and PR is submitted |
TEST | Team Lead | Tester/Product Owner | PR is merged by the maintainer and ready for Testing |
DONE | Tester/Product Owner | Tester/Product Owner | Test passed in both Development and Production environments. |
@thescientist13 @kpisano Above will be the final form of update^ any additional thoughts?
@saimatsumoto I think issue this can be closed now?
Type of Change
Summary
Proposed changes
To add below to Onboarding Guide:
Issue Status Transition
To ensure an effective task tracking, please use below as a guide on how to move issues via swim-lane in a project board:
Relates to #7