Workflow origin for the Jira issue closure loop. It creates exactly one owner-approved issue through recued-core.jira.issue.create, and when the issue succeeds it seeds durable data.shared closure state for jira-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, transition, assign, delete, comment on, attach to, link, watch, vote on, add worklogs to, or otherwise mutate Jira issues beyond the approved issue create.
Create Jira issue with closure watch
Workflow origin for the Jira issue closure loop. It creates exactly one owner-approved issue through recued-core.jira.issue.create, and when the issue succeeds it seeds durable data.shared closure state for jira-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, transition, assign, delete, comment on, attach to, link, watch, vote on, add worklogs to, or otherwise mutate Jira issues beyond the approved issue create.
Complete workflow
Jira Issue Closure Loop
4 pinned recipes
Workflow pack for Recued-created Jira issues. It composes the Jira capability pack with a closure ledger: create one owner-approved Jira issue in one configured cloud/project, persist only the connection/cloud/project/issue linkage in data.shared, and let a scheduled watcher re-read that exact issue until Jira reports the issue has reached the Done status category. This pack does not replace Jira workflow transitions, assignments, boards, sprints, automations, native notifications, webhooks, comments, worklogs, labels, due dates, or general issue reporting; it adds Recued-visible closure state for Jira issues Recued created.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Scheduled adopter for Jira issue closure rows seeded by create-jira-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of Jira issue, and closes the shared row when Jira reports that issue has reached the Done status category. It can notify the owner on closure, but it never creates, updates, transitions, assigns, deletes, attaches to, links, watches, votes on, comments on, adds worklogs to, or otherwise mutates Jira issues.
Low-frequency timeout role for recued-core/jira-issue-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Owner-visible list/close role for recued-core/jira-issue-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (32 steps)
cloud_id_value
trim
Trim whitespace from setting cloud id
project_key_value
trim
Trim whitespace from setting project key
issue_type_value
trim
Trim whitespace from setting issue type
summary_value
trim
Trim whitespace from setting summary
description_value
trim
Trim whitespace from setting description
has_connection
compare
Check if setting atlassian has data
has_cloud_id
compare
Check if cloud id value has data
has_project_key
compare
Check if project key value has data
has_issue_type
compare
Check if issue type value has data
has_summary
compare
Check if summary value has data
skip_issue_create
any
Check if any of the conditions are true
created_issue
?
skip: step.skip_issue_create equal true
created_issue_key
default
Apply default
created_issue_id
default
Apply default
created_issue_ref
default
Apply default
has_created_issue_ref
compare
Check if created issue ref has data
created_at
date_add
Add 0 days to
raw_watch_key
join
Join items with ":"
watch_key_colon
replace
Replace text in raw watch key
watch_key_slash
replace
Replace text in watch key colon
watch_key_dot
replace
Replace text in watch key slash
watch_key_at
replace
Replace text in watch key dot
watch_key_space
replace
Replace text in watch key at
watch_key_left_angle
replace
Replace text in watch key space
watch_key_right_angle
replace
Replace text in watch key left angle
watch_key_plus
replace
Replace text in watch key right angle
watch_key_equals
replace
Replace text in watch key plus
watch_key_question
replace
Replace text in watch key equals
skip_closure_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_jira_issue_closure_watch
?
skip: step.skip_closure_seed equal true
summary
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
summary
setting
=
cloud id
setting
=
atlassian
setting
=
issue type
setting
=
Task
description
setting
=
project key
setting
=
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.