Jira Project’s Documents
-
Why do we need it (points from sophiabilyk & Ivan Hodoniuk)
-
Create project’s space in Confluence
Tasks rules
-
Description in English + good examples
-
QA scope – Ivan Hodoniuk few tips / good examples how to describe it better
-
Assignee change after changing status from “In progress“ to “Ready for QA“
-
Only reporter can close the ticket (in case if QA was reported bug, only he can close it after check-up)
Project’s Workflow
-
General workflow process description (Dev → QA / CodeReview (later))
-
Differences between Status / Column
-
Presentation of the standard workflow scheme
Transitions need to be double-checked by sophiabilyk
-
How to add workflow scheme to your project
QA Resources
-
Divide QA resources by PMs, make the – Ivan Hodoniuk few words why do we need it, what are advantages of this model from QA team perspective
-
Ask PMs who they prefer to work with & make a table

Leave a Reply
You must be logged in to post a comment.