Support & answers
Help for Korbition products, starting with Rulekestra for Jira: documentation, direct engineering support, and clear paths for bugs, billing and security.
How to get help
✉️ Email support
[email protected]
Every ticket is answered by an engineer. Include your Jira site URL (e.g. yourcompany.atlassian.net), the rule name, and a run ID if you have one.
📝 Contact form
korbition.com/contact
Same inbox as email — use the form if you prefer, and we will reply to the address you leave.
📚 Documentation
Rulekestra knowledge base
Setup, triggers, conditions, actions, smart values, templates and migration — searchable, always current.
Pro subscriptions include priority engineering support and architectural guidance for rollout and migration. On every tier, support questions go to the same engineers who build the product.
Documentation & knowledge base
- Rulekestra KB — getting started, rule anatomy, triggers, conditions, actions, smart values and the 52 ready-made templates.
- Documentation home — all Korbition product docs in one place.
- Product page — feature overview, screenshots and pricing tiers.
Self-serve tools in the product
Most operational questions are answered inside Rulekestra itself, by the product's own tooling:
- Execution receipts — every condition, branch, skip and API call is recorded per run, so a "why didn't it fire?" question has a real answer.
- Dead-letter queue — transient failures retry with backoff; permanent failures land in a retryable queue an admin can work from the UI.
- Dry-run & backtest — preview what a rule would do against a sample event or historical issues before enabling it.
- Rule version history — every save is versioned with one-click restore.
Billing & licensing
Rulekestra is billed through Atlassian: billing, renewals, refunds and subscription changes are handled by Atlassian under Atlassian's Marketplace Terms of Use, managed from your Atlassian administration. License and tier questions can also come to us at [email protected].
Bugs & feature requests
- Bugs — email [email protected] with the rule name, run ID and what you expected. Receipts give us the exact execution trace, which makes most reports reproducible on the first reply.
- Feature requests — send to the same address; they are triaged weekly.
- Security vulnerabilities — [email protected], private disclosure, acknowledged within 2 business days. We follow Atlassian's Security Bug Fix Policy. Please do not disclose publicly before a fix ships.
Incidents & status
Platform incidents are communicated to affected tenants by email. Run-level failures are always visible in-product via execution receipts and the dead-letter queue — you never need to ask us whether a rule ran.
Data & privacy
- Privacy policy — what we store, for how long, and how it is protected.
- Trust center — security posture, data residency (EU / Frankfurt), sub-processors and legal documents.
- Data access and deletion requests — [email protected].