Feature & Issue workflow

Example Board

Open Issue

• Issue is created by anybody
• Is triaged, prioritized and has a milestone assigned
• Issue includes enough information (follows template) that allows team members to estimate, understand the scope, user benefit, the what, and acceptance criteria

Ready for UX

• When UX picks up issue, assign themselves to the issue
• UX to provide mocks, attach to Github issue
• Once UX is done, ready for eng, UX resource to unassign themselves, and use "ready for eng breakdown" label

Ready for Eng

• Eng should only pick up issues that are ready for Eng and assigned to a sprint/milestone (not Backlog)

Eng done

• Issue is eng done only if PR was submitted AND PR was reviewed
• PR is closed but not issue
• Issue will be assigned by eng to product manager (PM assigns it to other stakeholders where appropriate )

Stakeholder review

• During sprints: Once PR is closed, the next day Nightly should have the changes and stakeholders can verify
• During sprint review: everyone can review, comment
• Once stakeholders are happy with result, PM assign "ready for QA" label and

Ready for QA

• QA to watch for issues with "ready for QA" label AND in current sprint or major milestone
• QA to assign the ticket they are currently working on to themselves
• Once QA verified and completed issue, un-assign themselves from issue
• Closes issue

Done

• Issue is closed, no assignees and assigned sprint or major milestone