Approval-gated Bitbucket Cloud issue creation workflow. It reads the authenticated user and target repository for context, then creates exactly one issue with bounded title, Markdown body, kind, and priority through recued-core.bitbucket. It does not update or delete existing issues, change assignees, upload attachments, change repository settings, run pipelines, create webhooks, or call arbitrary Bitbucket APIs.

How it works 10 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (10 steps)

■ workspace trim

Trim whitespace from setting workspace

■ repo_slug trim

Trim whitespace from setting repo slug

■ title trim

Trim whitespace from setting title

■ content trim

Trim whitespace from setting content

■ has_title compare

Check if title has data

■ viewer ?

■ repository ?

■ created_issue ?

skip: step.has_title not_equal true

■ skipped compare

Check if has title does not equal true

■ card to_summary

Format results as a summary card

Settings 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

kind setting = task

title setting =

content setting =

priority setting = major

bitbucket setting =

repo slug setting =

workspace setting =