Rulekestra Knowledgebase & Documentation

🚀 Quickstart & Installation

Rulekestra runs natively on Atlassian Forge Cloud. Once installed in your Jira instance, automation rules execute with zero server provisioning and strict per-tenant isolation.

1. Install from Atlassian Marketplace

Add Rulekestra to your Jira Cloud site with standard Jira Administrator permissions. No external agent or database configuration required.

2. Launch the Visual Orchestrator

Access Rulekestra directly from project settings or the global apps menu. Author workflows using either the interactive canvas or AI prompt generator.

3. Grant Least-Privilege Scopes

Connect your team channels (GitHub, GitLab, Slack, Teams, Google) using project-scoped OAuth 2.0 authorizations.

4. Test & Publish with Truthful Receipts

Run simulated dry-runs or live triggers to inspect every evaluated condition and execution step in real-time audit logs.

⚡ Deep Smart Values Reference

Rulekestra provides type-safe, enriched context for Jira actors, changelogs, custom fields, and external payloads without requiring manual API lookups.

// Actor & Requester Attributes
{{actor.displayName}}        -> Full name of the initiating user
{{actor.email}}              -> Verified email via read:email-address:jira scope
{{actor.accountId}}          -> Canonical Atlassian Account ID

// Issue Context & Hierarchy
{{issue.key}}                -> PROJ-1024
{{issue.fields.summary}}     -> Incident: Elevated API Error Rate
{{issue.fields.priority}}    -> High / Critical
{{issue.parent.key}}         -> Parent Epic or Initiative Key
{{issue.subtasks}}           -> Iterable list of child sub-tasks

// Changelog & Diffs
{{changelog.status.from}}    -> "In Progress"
{{changelog.status.to}}      -> "Pending Review"
{{changelog.assignee.to}}    -> New Assignee details
        

🐙 GitHub & 🦊 GitLab Enterprise Connectors

Link Jira workflow triggers and actions directly to your code repositories, pull requests, and CI/CD pipelines with bidirectional synchronization.

GitHub Pull Request Triggers

Automatically transition Jira issues, assign reviewers, or comment when PRs are opened, reviewed, approved, or merged.

PR Events Branch Deploy Gates Commit Status Checks

GitLab Merge Request & CI Sync

Listen for pipeline success/failure webhooks, protected branch pushes, and automated release tag deployments linked to Jira tickets.

Pipeline Triggers Merge Requests Issue Bi-Sync

// Example: GitHub Webhook Smart Value in Rulekestra Action
{{webhookData.pull_request.title}}     -> "feat(auth): Add SAML SSO bridge"
{{webhookData.pull_request.html_url}}  -> "https://github.com/org/repo/pull/42"
{{webhookData.pull_request.user.login}}-> "octocat"
        

💬 Slack, Microsoft Teams & Confluence

Orchestrate human-in-the-loop approvals and collaborative updates without team members ever leaving their primary chat tools.

Interactive Slack Cards

Dispatch Block Kit cards featuring "Approve", "Decline", or "Request Details" buttons that immediately resume parked Jira execution branches.

Microsoft Teams Adaptive Cards

Native Entra multi-tenant integration delivering actionable cards into designated Teams channels with authenticated button callbacks.

Confluence Automated Documentation

Create or update Confluence pages automatically (e.g., Post-Mortems, Release Notes, Sprint Summaries) formatted with rich ADF layout blocks.

Google Workspace / Gmail Dispatch

Send operational notification emails via verified Google OAuth 2.0 with minimal gmail.send authorization scopes.

🛡️ Enterprise Security & Tenant Isolation

Rulekestra is architected around strict least-privilege scoping, zero cross-tenant credential leakage, and full Atlassian Cloud security compliance.

As-User Execution Model

Every write operation is bound to the verified permissions of the initiating Jira actor or authorized rule author to prevent privilege escalation.

Cryptographic Credential Storage

All third-party OAuth access tokens and client secrets are encrypted at rest using isolated per-tenant keyrings.

Resilient Dead-Letter Queues

Transient network failures or downstream rate limits are queued and automatically retried with exponential backoff.

Zero-Data-Retention Policy

Payloads are processed in-memory during execution lifecycle only; no persistent copies of customer ticket content are stored.