typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
some big and monolith issues. For example with hard decisions or discussions
performer can implement issue at his closest convenient time
we can defer this issue. But it'll good to implement it
small issues. Usually cosmetic fixes
small issues. Usually cosmetic fixes
adapt admin to the options, tag and db templates integration
issue is blocked by another issue
this issue blocks another issue
everything that do project stronger, flexible, reusable
Feature about migrating data on prod
Pull requests that update a dependency file
work with service options with code or with configs
issue needs to finish discussion before start working
issue for improving project's documentation
new teammates can start with such issues to become familiar with project
issue provides some new functionality for project users
from product owner. It's hellxi
issue requires strong architecture skills, management skills, project domain area, etc
issue needs additional requirements to start working