CRITICAL (If active, do not ship product)
Development operations efficiency (automation, etc)
HIGH PRIORITY (If active, product is shippable with minor workflow errors)
LOW PRIORITY (If active, product is fully shippable)
NICE TO HAVE (If active, product is fully shippable)
Add specs, priority and LOE to task
Dependent on resolving another issue (include #) or blocker (business administration, etc)
Includes new UI/UX designs
Issue or pull request already exists (include issue #)
Tokes (TKS) eCommerce platform
New feature or enhancement to existing feature
Tokes (TKS) merchant gateway API
Extra attention is needed
Revise issue before triage (doesn't seem right, split into multiple issues, better define, etc)
Doesn’t make sense to estimate LOE (team training, etc)
The task must be spread over smaller tasks
A task that is not complex
A task that is medium-complex
Complex issue. We avoid such issues by splitting them into smaller issues
Designed for a particular purpose. Engineers team pays special attention to the issue labeled LOE 5
Non-programming issue - used for Project Management task tracking
Further information is requested
Needs LOE diagnosis (LOE1 assumed to diagnose)