Name: Jira issue comment closure watcher
Author: recued-core

Jira issue comment closure watcher

by recued-core v1

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.

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.

Jira issue comment closure watcher

This recipe Background automation

jiraatlassianissuescomments

by recued-core pinned v1

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.

jiraatlassianissuescomments

by recued-core pinned v1

Jira issue comment closure watcher timeout

Background automation

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.

jirawatchertimeoutowner-review

by recued-core pinned v1

Jira issue comment closure watcher lifecycle review

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.

jirawatcherreviewclose

by recued-core pinned v1

View pack details, dependencies, and permissions →

How it works 95 steps

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

Data fetch

▼ shared_issue_watches ?

▼

Process (94 steps)

■ now date_add

Add 0 days to

■ watch_rows filter

Filter by condition

■ watch_rows_for_connection filter

Filter by condition

■ watch_rows_with_cloud filter

Filter by condition

■ watch_rows_with_issue filter

Filter by condition

■ never_checked_watch_rows filter

Filter by condition

■ checked_watch_rows filter

Filter by condition

■ checked_watch_rows_oldest_first sort

Sort by value.last_checked_at

■ fair_watch_rows flatten

Flatten nested lists in

■ candidate_rows slice

Take a subset of

■ batch_count count

Count items in candidate rows

■ candidate_count count

Count items in watch rows with issue

■ has_candidate compare

Check if candidate rows has data

■ has_connection compare

Check if setting atlassian has data

■ skip_issue_read any

Check if any of the conditions are true

■ batch_context_envelopes merge

Combine objects together

■ batch_contexts map

Extract from each item

■ issue ?

skip: step.skip_issue_read equal true

■ issue_live_batch_context pick

Keep only specific fields from

■ issue_batch_context_envelopes merge

Combine objects together

■ issue_batch_contexts map

Extract from each item

■ status_name default

Apply default

■ status_name_live_batch_context pick

Keep only specific fields from

■ status_name_batch_context_envelopes merge

Combine objects together

■ status_name_batch_contexts map

Extract from each item

■ status_category_key default

Apply default

■ status_category_key_live_batch_context pick

Keep only specific fields from

■ status_category_key_batch_context_envelopes merge

Combine objects together

■ status_category_key_batch_contexts map

Extract from each item

■ has_issue_status_category compare

Check if item status category key has data

■ has_issue_status_category_live_batch_context pick

Keep only specific fields from

■ has_issue_status_category_batch_context_envelopes merge

Combine objects together

■ has_issue_status_category_batch_contexts map

Extract from each item

■ status_category_key_norm lowercase

Convert item status category key to lowercase

■ status_category_key_norm_live_batch_context pick

Keep only specific fields from

■ status_category_key_norm_batch_context_envelopes merge

Combine objects together

■ status_category_key_norm_batch_contexts map

Extract from each item

■ issue_done compare

Check if item status category key norm equals done

■ issue_done_live_batch_context pick

Keep only specific fields from

■ issue_done_batch_context_envelopes merge

Combine objects together

■ issue_done_batch_contexts map

Extract from each item

■ live_issue_key default

Apply default

■ live_issue_key_live_batch_context pick

Keep only specific fields from

■ live_issue_key_batch_context_envelopes merge

Combine objects together

■ live_issue_key_batch_contexts map

Extract from each item

■ live_issue_id default

Apply default

■ live_issue_id_live_batch_context pick

Keep only specific fields from

■ live_issue_id_batch_context_envelopes merge

Combine objects together

■ live_issue_id_batch_contexts map

Extract from each item

■ live_project_key default

Apply default

■ live_project_key_live_batch_context pick

Keep only specific fields from

■ live_project_key_batch_context_envelopes merge

Combine objects together

■ live_project_key_batch_contexts map

Extract from each item

■ skip_close any

Check if any of the conditions are true

■ skip_close_live_batch_context pick

Keep only specific fields from

■ skip_close_batch_context_envelopes merge

Combine objects together

■ skip_close_batch_contexts map

Extract from each item

■ closed_watch_key replace

Replace text in item watch key

■ closed_watch_key_live_batch_context pick

Keep only specific fields from

■ closed_watch_key_batch_context_envelopes merge

Combine objects together

■ closed_watch_key_batch_contexts map

Extract from each item

■ close_watch ?

skip: item.skip_close equal true

■ close_watch_live_batch_context pick

Keep only specific fields from

■ close_watch_batch_context_envelopes merge

Combine objects together

■ close_watch_batch_contexts map

Extract from each item

■ delete_closed_active_watch ?

skip: item.close_watch.ok not_equal true

■ delete_closed_active_watch_live_batch_context pick

Keep only specific fields from

■ delete_closed_active_watch_batch_context_envelopes merge

Combine objects together

■ delete_closed_active_watch_batch_contexts map

Extract from each item

■ notify_enabled compare

Check if setting notify when done equals true

■ notify_enabled_live_batch_context pick

Keep only specific fields from

■ notify_enabled_batch_context_envelopes merge

Combine objects together

■ notify_enabled_batch_contexts map

Extract from each item

■ should_notify all

Check if all conditions are true

■ should_notify_live_batch_context pick

Keep only specific fields from

■ should_notify_batch_context_envelopes merge

Combine objects together

■ should_notify_batch_contexts map

Extract from each item

■ notify_owner ?

skip: item.should_notify not_equal true

■ notify_owner_live_batch_context pick

Keep only specific fields from

■ notify_owner_batch_context_envelopes merge

Combine objects together

■ notify_owner_batch_contexts map

Extract from each item

■ refreshed_watch_value merge

Combine objects together

skip: item.delete_closed_active_watch.ok equal true

■ refreshed_watch_value_live_batch_context pick

Keep only specific fields from

■ refreshed_watch_value_batch_context_envelopes merge

Combine objects together

■ refreshed_watch_value_batch_contexts map

Extract from each item

■ refresh_active_watch ?

skip: item.delete_closed_active_watch.ok equal true

■ refresh_active_watch_live_batch_context pick

Keep only specific fields from

■ refresh_active_watch_batch_context_envelopes merge

Combine objects together

■ refresh_active_watch_batch_contexts map

Extract from each item

■ closed_batch_rows filter

Filter by condition

■ refreshed_batch_rows filter

Filter by condition

■ closed_batch_count count

Count items in closed batch rows

■ refreshed_batch_count count

Count items in refreshed batch rows

■ summary to_summary

Format results as a summary card

Settings 4 configurable

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

channels setting = in_app

atlassian setting =

batch limit setting = 5

notify when done setting = true

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Send notificationsRead your Atlassian connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.shared

About

recued-core

Details

95 steps 4 configurable settings recipe_id: jira-issue-comment-closure-watcher

Jira issue comment closure watcher

Complete workflow

Trust & control

Where it runs

Permissions it requires

Data it touches

About

Tags

Details