Skip to content

Latest commit

 

History

History
22 lines (16 loc) · 991 Bytes

ISSUE_TEMPLATE.md

File metadata and controls

22 lines (16 loc) · 991 Bytes

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour/error

Where does this issue happen?

It is ready for development when

  • Has a description that includes purpose of this particular feature/improvement (how it will help the user and for which use cases)
  • Can be delivered within a sprint (make sure issues are small pieces of work, not huge epics)
  • Has all designs and UI assets available
  • Has all (probable) dependencies identified
  • Is estimated by the team
  • Has acceptance criteria defined (do we want to do this before we send to dev? might help us identify dependencies/holes earlier?)