Skip to content

No labels!

There aren’t any labels for this repository quite yet.

1 hour
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
1
1
burning issue
2 hours
2 hours
some big and monolith issues. For example with hard decisions or discussions
2
2
performer can implement issue at his closest convenient time
3
3
we can defer this issue. But it'll good to implement it
15 mins
15 mins
small issues. Usually cosmetic fixes
30 mins
30 mins
small issues. Usually cosmetic fixes
blocked
blocked
issue is blocked by another issue
blocker
blocker
this issue blocks another issue
Cache
Cache
feature
cleanup
cleanup
everything that do project stronger, flexible, reusable
Context
Context
feature
Control Panel
Control Panel
dependencies
dependencies
Pull requests that update a dependency file
devops
devops
work with service options with code or with configs
discuss
discuss
issue needs to finish discussion before start working
docs
docs
issue for improving project's documentation. Tech writers can perform some of this issues
duplicate
duplicate
easy
easy
new teammates can start with such issues to become familiar with project
feature
feature
issue provides some new functionality for project users
from business
from business
from PO
from PO
from product owner. It's hellxi
front
front
hard
hard
issue requires strong architecture skills, management skills, project domain area, etc
help wanted
help wanted
invalid
invalid
monitoring
monitoring
needs info
needs info
issue needs additional requirements to start working