Jira
Issues, sprints, and transitions on Jira
Jira is the enterprise issue tracker your security team probably mandated, and Tiny Command treats its workflow-state machine as a first-class concept. Six triggers cover the lifecycle that matters in agile delivery: Issue Created, Issue Updated, Issue Deleted, Comment Created, Sprint Started, and Sprint Closed. Seventeen actions handle the operational side, but two of them are distinctive: Transition Issue respects the project's workflow (you can only move an issue to a state that's a valid next-step from its current state), and Get Transitions returns the valid transitions for any given issue at runtime, so a workflow can decide which transition is legal before attempting it. The other actions cover Create Issue, Update Issue, Assign Issue, Add Comment, Add Watcher, Link Issues, Search Issues (with full JQL support), and the read endpoints for projects, sprints, statuses, and issue types. Authorize via Atlassian OAuth; the connection respects Jira project-level permissions.
Workflows start when Jira does.
6 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.
Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.
Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.
Fires whenever any field on a Jira issue changes (status, assignee, priority, custom fields). Combine with a field filter to react only to the changes you care about.
Fires when a sprint is closed in Jira. Use to roll up sprint metrics, generate a retrospective doc, or auto-create the next sprint.
Fires when a sprint is started in Jira. Useful for kicking off stand-up bots, posting sprint goals to Slack, or seeding a sprint-board template.
Do anything Jira can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add Comment | Adds a comment to an existing Jira issue with optional visibility restriction (role or group). Used for automation activity logs, AI summary notes, or external system pings. |
| Add Watcher | Adds a user as a watcher on a Jira issue so they receive notifications on updates. Used to auto-loop in interested parties (PMs, designers, support). |
| Assign Issue | Assigns a Jira issue to a user (by accountId) or unassigns it. The standard routing action for AI-driven triage or rotating on-call assignment. |
| Create Issue | Creates a new issue (story, task, bug, epic, etc.) in a Jira project with summary, description, type, assignee, priority, labels, components, and custom fields. Standard write for converting external alerts into tracked work. |
| Delete Issue | Permanently deletes a Jira issue by key or ID. Irreversible; pass deleteSubtasks=true to also remove children. Most teams transition to a Cancelled status instead. |
| Get Issue | Retrieves a Jira issue by its key (ABC-123) or numeric ID with summary, description, status, assignee, comments, and custom fields. The standard read after a trigger fires with an ID. |
| Get Project | Returns details of a Jira project: name, key, lead, issue types, components, and versions. Used to enrich a trigger or validate a project reference. |
| Get Sprint Issues | Returns all issues in a Jira sprint. Used for stand-up dashboards, sprint reviews, or burndown reporting outside Jira. |
| Get Transitions | Returns the available status transitions for an issue based on the workflow it's on. Required before calling Transition Issue, since you pass a transition ID, not a status name. |
| Link Issues | Creates a link between two Jira issues (blocks/is blocked by, relates to, duplicates, etc.). Used to maintain cross-issue relationships from automated triage. |
| List Issue Types | Lists all issue types available in Jira (Story, Task, Bug, Epic, custom types). Use to populate a type picker before creating an issue. |
| List Projects | Lists all Jira projects accessible to the authenticated user with key, name, and lead. The standard first step before scoping work to a project. |
| List Sprints | Lists all sprints for a Jira board with state (future, active, closed) and dates. Useful for sprint pickers and reporting. |
| List Statuses | Returns all issue statuses available in the Jira instance with their categories. Useful for filtering and for validating status names before a transition. |
| Search Issues (JQL) | Searches for issues using JQL (Jira Query Language), the full-featured query syntax. Powers SLA dashboards, segment reports, and complex upsert lookups. |
| Transition Issue | Changes the status of a Jira issue (e.g. To Do to In Progress to Done) by transition ID. Get the available transition IDs via Get Transitions first. |
| Update Issue | Updates fields on an existing Jira issue: summary, description, priority, assignee, labels, components, custom fields. Only the fields you pass are changed. |
Pre-built Jira workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Jira once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Jira field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Jira integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Jira to Tiny Command?
What Jira triggers does Tiny Command support?
What Jira actions can I run from a workflow?
Is the Jira integration real-time?
Do I need to write code to use Jira with Tiny Command?
How much does the Jira integration cost?
More developer tools apps people connect.
Same category as Jira, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Jira.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
