Workflow origin for the Jira issue comment closure loop. It reads one Jira issue and current comments for context, creates exactly one owner-provided Atlassian Document Format comment through recued-core.jira.comment.add, and when the comment succeeds it seeds durable data.shared closure state for jira-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, assign, delete, attach to, link, watch, vote on, or otherwise mutate Jira issues.
Comment on Jira issue with closure watch
Workflow origin for the Jira issue comment closure loop. It reads one Jira issue and current comments for context, creates exactly one owner-provided Atlassian Document Format comment through recued-core.jira.comment.add, and when the comment succeeds it seeds durable data.shared closure state for jira-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, assign, delete, attach to, link, watch, vote on, or otherwise mutate Jira issues.
Complete workflow
Jira Issue Comment Closure Loop
4 pinned recipes
Workflow pack for Recued-created Jira issue comments. It composes the Jira capability pack with a closure ledger: add one owner-approved Atlassian Document Format comment to an existing Jira issue, persist only the connection/cloud/issue/comment 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 issue comments, native notifications, workflow transitions, assignments, boards, sprints, automations, webhooks, or general issue reporting; it adds Recued-visible closure state for issue comments 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 comment closure rows seeded by comment-jira-issue-with-closure. It lists only Recued-originated issue-comment 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, or otherwise mutates Jira issues.
Low-frequency timeout role for recued-core/jira-issue-comment-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-comment-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 (41 steps)
cloud_id_value
trim
Trim whitespace from setting cloud id
issue_id_or_key_value
trim
Trim whitespace from setting issue id or key
comment_text_value
trim
Trim whitespace from setting comment text
has_connection
compare
Check if setting atlassian has data
has_cloud_id
compare
Check if cloud id value has data
has_issue_id_or_key
compare
Check if issue id or key value has data
has_comment_text
compare
Check if comment text value has data
skip_issue_read
any
Check if any of the conditions are true
issue
?
skip: step.skip_issue_read equal true
live_issue_key
default
Apply default
live_issue_id
default
Apply default
project_key
default
Apply default
status_name
default
Apply default
status_category_key
default
Apply default
has_issue_status_category
compare
Check if status category key has data
status_category_key_norm
lowercase
Convert status category key to lowercase
issue_already_done
compare
Check if status category key norm equals done
skip_comment_context
any
Check if any of the conditions are true
comments_raw
?
skip: step.skip_comment_context equal true
comments
default
Apply default
comment_count_before_create
count
Count items in comments
skip_comment_create
any
Check if any of the conditions are true
created_comment
?
skip: step.skip_comment_create equal true
created_comment_id
default
Apply default
has_created_comment
compare
Check if created comment id 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_comment_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.
cloud id
setting
=
atlassian
setting
=
comment text
setting
=
issue id or 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.