Automations
Automations, planned for RyTask — trigger, condition, action rules that auto-assign, move, label, or call a webhook, with unlimited runs because you self-host.
RyTask plans an automation engine built on trigger → condition → action rules: when a status changes, assign someone, move the item, add a label, or call a webhook. The structural advantage is unlimited automation runs — every SaaS competitor meters them (Jira around 100, ClickUp 100, Trello 250, Monday caps too), but there is nothing to meter when the software runs on your own server.
What's planned:
- Trigger → condition → action rules — basic rules first (MVP scope), full builder later (v2).
- Unlimited runs — the self-host advantage; no caps (MVP scope).
- Status-change automations — auto-assign, auto-move, auto-label (MVP scope).
- Webhook actions — call an external URL when a rule fires (MVP scope).
- Scheduled automations — time-based triggers (v2).
- Recipe packs — prebuilt rule templates (v2).
- Cross-entity automations — rules that span projects (v3).
Roadmap (coming soon)
One page per planned capability cluster — what RyTask intends to build, with tiers, and nothing pretending to be shipped.
Custom fields
Custom fields, planned for RyTask — text, number, select, date, and user fields on work items first, with validation and computed fields later. No usage caps.