Short answer: You can create issue in Bitbucket by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitbucket Create Issue action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Workspace workspace | string | Required | Workspace. Example: my-team |
Repository Slug repo_slug | string | Required | Repository Slug. Example: my-project |
Title title | string | Required | Title. Example: Fix broken CI pipeline |
Description content | string | Optional | Markdown description |
Kind kind | options | Optional | Kind. Options: Bug, Enhancement, Proposal, Task |
Priority priority | options | Optional | Priority. Options: Trivial, Minor, Major, Critical, Blocker |
{"workspace": "e.g. my-team","repo_slug": "e.g. my-project","title": "e.g. Fix broken CI pipeline","content": "{{trigger.content}}","kind": "{{trigger.kind}}"}
{"id": 1,"kind": "bug","links": {"html": {"href": "https://bitbucket.org/team/project/issues/1"}},"state": "new","title": "Fix broken CI","priority": "major"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.